I'm running Zope 2.5.1 under Windows 2000 on a P3-500 machine. I start it manually as a service. The service seems to start quickly (it says it's started after 5 seconds or so), but it's another 30 seconds or so until I can access the server. I've watched the task manager while it's starting up, and it's the python.exe process that is using up CPU time during the wait. I just assumed 30 seconds was the normal startup time. On a 667 MHz G4 Powerbook (OSX 10.1.5), the Zope server takes 20-25 seconds to start. Barry Berenberg
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of EvH Sent: Friday, July 26, 2002 2:16 AM To: zope@zope.org Subject: [Zope] Re: Speeding up Zope startup
At 21:19 24/07/2002 +0200, Dieter Maurer <dieter@handshake.de> wrote:
This is almost surely a DNS problem.
No, I don't think it is, because the Windows host where Zope is running can resolve its adresse thanks to a "hosts" file (of a DNS server when my test Linux host is running :-) ), and the part d:\Program Files\WebSite>"D:\Program Files\WebSite\bin\python.exe" "D:\Program F iles\WebSite\z2.py" -D", but at that time, I can hear the hard-disk having the time of its life, so I guess Zope is trying to build/rebuild indexes or something.
Is anyone else running Zope on a Windows workstation (P3) and witnessing a good 30-s delay until Zope is up and running? BTW, I installed Zope on one of my brother's PCs (a P2), and it's close to a minute...
Thx Fred.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )