Paul Erickson wrote:
Just for kicks, why don't you see what system calls it is using. If it's not doing any, then the odds are that there's some sort of internal processing going on inside of zope. I've seen this occasionaly with zope 2.3 if a bunch of products have changed, but after it is running then performance is fine.
Get the pid from top that is using up the cpu and run
strace -p your_pid
You will probably have to run it as either the user that started zope or root.
Done that. It's very interesting to do this while zope is starting up. It seems the last 10 of my seconds zope is in a tight loop calling time() and doing nothing else. If I do strace -p on a thread that processes an HTTP request, strace immediately exits without displaying anything (maybe because strace does not support threads?) I'll try upgrading strace in a moment. Note: this is a RedHat 7.0 system. Ron Arts