Matthew T. Kromer wrote:
Ron, just to make sure, you do have DMA enabled on your hard drives, right? hdparm should tell you that status. If you don't, then you'll suffer greatly when you need to do I/O because all of the bytes are running through the CPU.
Some more data points, we have the same problem on a dev server, linux 2.2.13 The funny thing is, this happened after rebooting the server when we installed a scsi drive, before everything was ok. The scsi drive does make some problems, and it might not be related directly to zope - I suspect the drive, but anyway, perhaps it's something else. Ron, what OS are you running? If linux, could you repeat the steps I did for comparision?
dmesg (fruitless, because dmesg is filled up with scsi-errors) hdparm -t /dev/<of all disk devices>
/dev/hda: Timing buffered disk reads: 32 MB in 2.65 seconds =12.08 MB/sec
hdparm -T /dev/<of all disk devices>
/dev/hda: Timing buffer-cache reads: 64 MB in 0.61 seconds =104.92 MB/sec
time start (use -D option and press ctrl-C as soon as you see it has started up)
------ 2002-03-14T16:45:18 INFO(0) ZServer HTTP server started at Thu Mar 14 17:45:18 2002 Hostname: baal.compuvision Port: 10080 Traceback (innermost last): File "/home/zope/Zope-2.3.3-src/z2.py", line 772, in ? asyncore.loop() File "/home/zope/Zope-2.3.3-src/ZServer/medusa/asyncore.py", line 146, in loop poll_fun (timeout, map) File "/home/zope/Zope-2.3.3-src/ZServer/medusa/asyncore.py", line 70, in poll try: r,w,e = select.select (r,w,e, timeout) KeyboardInterrupt Traceback (innermost last): File "/home/zope/Zope-2.3.3-src/z2.py", line 548, in ? zdaemon.run(sys.argv, os.path.join(CLIENT_HOME, Zpid)) File "/home/zope/Zope-2.3.3-src/lib/python/zdaemon.py", line 209, in run p,s = os.waitpid(pid, 0) KeyboardInterrupt real 0m20.928s user 0m13.160s sys 0m0.790s You see, this is quite long. No special products installed.