Am Donnerstag, 26. Februar 2004 17:17 schrieb Poor, Edmund W:
I agree with Brion, and I'm sorry I replied to
Timwi before reading
Brion's "I forbid" post.
I've done profiling on Visual Basic 4.0 & 5.0, MS SQL Server 6.5, and
Java; and let me tell you I'm frequently amazed at the kinds of things
that cause slow spots. "But that can't be true!" is the usual response
of my colleagues. Then, you show them the profiling data, and they're
like, "Well, I'll be durned. Who would have known?"
Anyone know how to profile MySQL code?
You should keep in mind that profiling does not always show you the code which
is slow or should be improved! Often bad code occures on diffrent places.
For example one function, routine, methode or what ever calls another very
often. The profiler will show you the often called function. But the best way
is not to improve the called function. The best way is to optimize the
calling function that way, that it does not need to call the otherone so
Thus you always have to understand your code, even if you profile it. And if
you really undersand your code you seldom need to profile it to know were to