So do we know what the cause of the 500 ms slowdown was?
It seems crazy to me that they spend so much time keeping this hidden and then never check for performance degradation.
It seems crazy to me that they spend so much time keeping this hidden and then never check for performance degradation.
They were rushing to get it out into the wild and thus made many mistakes, including the performance degradation.
From what I recall, some distros were reporting build errors in bleeding edge versions. Actors were essentially debugging issues in production, and recommending to distro maintainers ways to “fix” (really hide) the build issue with xz
Normally it would be much quicker but potentially could have been picked up downstream by other developers when the code became more mainstream.
He did an interview for Risky Business #743.