Possible Threading problem with -CURRENT / MySQL?
amd64list at jpgsworld.com
Wed Jun 16 04:09:45 GMT 2004
>As I suggested elsewhere:
>To check this you should try running systat -vmstat
>while noticing the slowdown and try see what is at 100%.
>if it turns out that you are NOT seeing disk or CPU limitted
>then the next step would be to take a snapshot of operations using
>ktrace -d -p (pid) for 20 second followe by krtace -C to turn it off
>then looking at the output may give an idea of what operations are
>taking too long, and what is waiting on what..
I think I'll wait for someone more qualified to evaluate these problems.
I can't code, don't have commit access, and don't even know how to see
what was added or removed to -CURRENT when or where etc.
The problem has been laid on the table of the FreeBSD gods by many
people now. FreeBSD would be dead in the water if it relied on the likes
of me to do assessments and debugging.
Once I identified what was taking too long and what was waiting on what
- I would have no clue what to do or try from there, but I'm sure it would
require some coding experience.
More information about the freebsd-threads