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. -Paul Ron Arts wrote:
seb bacon wrote:
If you have a large Data.fs with a lot of products, it is normal to see a long startup time. But if this was a fresh Zope, then I would not expect the startup on your hardware to take more than 15 seconds at the most.
There are two possibilities:
1) Your system has a bottleneck you aren't aware of, processes blocking, running out of file descriptors, etc. 2) Python or Zope has some bug w.r.t your system.
Here are some questions for you:
What is your load average? CPU utilization? Disk activity? Perhaps you could post a 'vmstat 2 10' the system idling vs. starting up zope vs. viewing a page in started up Zope?
System idle:
[root@n010080 /root]# vmstat 2 10 procs memory swap io system cpu r b w swpd free buff cache si so bi bo in cs us sy id 0 0 0 4772 3208 5888 32576 0 0 6 3 27 49 95 4 1 0 0 0 4772 3208 5888 32576 0 0 0 0 188 52 2 4 94 0 0 0 4772 3208 5888 32576 0 0 0 0 218 89 7 16 77 0 0 0 4772 3208 5888 32576 0 0 0 0 177 52 1 4 94 0 0 0 4772 3208 5888 32576 0 0 0 0 187 59 3 3 94 0 0 0 4772 3208 5888 32576 0 0 0 0 210 92 8 14 78 0 0 0 4772 3208 5888 32576 0 0 0 0 197 57 2 3 94 1 0 0 4772 3212 5888 32576 0 0 0 0 225 98 7 17 77 0 0 0 4772 3208 5888 32576 0 0 0 0 194 79 1 6 93 0 0 0 4772 3208 5888 32576 0 0 0 0 200 51 2 4 94
Zope start
[root@n010080 /root]# vmstat 2 10 procs memory swap io system cpu r b w swpd free buff cache si so bi bo in cs us sy id 1 0 0 4772 16088 5380 32320 0 0 6 3 27 49 95 4 1 1 0 0 4772 15524 5380 32320 0 0 0 7 223 53 80 20 0 1 0 1 4772 13800 5800 32320 0 0 0 171 1337 110 73 27 0 2 0 0 4772 12776 5800 32320 0 0 0 7 470 71 83 17 0 1 0 0 4772 12308 5800 32320 0 0 5 1 194 64 91 9 0 1 0 0 4772 11640 5800 32320 0 0 0 0 179 56 90 10 0 1 0 0 4772 11004 5800 32320 0 0 2 0 203 58 87 13 0 1 0 0 4772 10420 5800 32320 0 0 0 0 192 50 89 11 0 1 0 0 4772 10308 5800 32320 0 0 0 1 162 53 95 5 0 1 0 0 4772 9580 5800 32320 0 0 0 0 173 49 92 8 0
Viewing a page:
[root@n010080 /root]# vmstat 2 10 procs memory swap io system cpu r b w swpd free buff cache si so bi bo in cs us sy id 1 0 0 4772 2452 6372 32408 0 0 6 3 28 49 95 4 1 1 0 0 4772 2428 6372 32416 0 0 1 0 200 57 93 7 0 1 0 0 4772 2412 6372 32428 0 0 0 2 203 60 94 6 0 1 0 0 4772 2392 6372 32432 0 0 0 0 193 51 91 9 0 2 0 0 4772 2328 6372 32448 0 0 1 0 221 84 91 6 3 1 0 1 4772 2216 6372 32468 0 0 0 2 224 77 89 11 0 2 0 3 4772 2156 6372 32524 0 0 6 0 245 73 86 11 3 1 0 2 4772 2140 6372 32544 0 0 1 0 180 58 92 8 0 1 0 0 4772 3108 6132 32336 0 0 4 0 239 62 80 18 2 1 0 0 4772 3072 6132 32360 0 0 2 32 464 81 78 20 2
What OS are you running? IIRC there have been problems with threads on solaris.
Linux 2.2.20 kernel.
Did you compile python, zope from source? What version of python are you using? What flags did you compile it with?
I used the RPM that is on www.zope.org, recreated that using the newest Zope version (only thing I needed to change was add some products to the spec file). The Zope RPM is running fine withouth CMF and plone.
If I add CMF it gets a lot slower, but when I add plone it really sucks.
Magnus said:
3) You have used a cvs CMF version too long ;-) My guess is that 7 minutes on a P233 to login is normal, if you are using Plone that uses PageTemplates, and CMF1.2 that does not have support for delayed cooking.
There is a HUGE difference in startup time/first access time when using CMF cvs with delayed PageTemplates cooking support.
So if I want to use plone I need to use latest CMF CVS-version? I did not know that, the docs said CMF 1.2 was OK, so I took it. I generally prefer not to use CVS versions.
Ron Arts