3 ms·
This is a great example of why it's important to actually determine the root cause of a performance problem before making any decisions about how to fix it. Per
by paul 18y ago
This is a great example of why it's important to actually determine the root cause of a performance problem before making any decisions about how to fix it. Performance problems are very often something stupid and not at all what you would expect.
- wheels 18y agoAmen. I've seen way too many code-bases hacked to death by insistence on things being "fast" without at all understanding what or where the slowdowns might be. Monte-Carlo optimization, I suppose. ;-)
- spc476 18y agoBut I have to wonder how RedHat is compiling the packages. A few years ago I was bit with this, when the system supplied regex library I was linking against (I was writing a C program) was actually slower than a shell script with 20 greps in a pipe (http://boston.conman.org/2003/01/12.1 http://boston.conman.org/2003/01/12.1). This took quite a while to track down and even then I found it hard to understand what RedHat did when compiling the library in question. Way to go, RedHat!
- maw 18y agoIt's pretty easy to find out by pulling down one of their srpms, or by looking at fedora cvs. Why don't you do that?