Urk. OK - My Zope installation had died, apparently. I started to get the PCGI process dying and those long timeouts I mentioned, so I just rebuilt Zope from scratch and exported/imported the application - it's all super-snappy now <sigh> Sorry for the false alarm - but it did seem to degrade without any external input, and a "Pack" attempt on the database failed with "I/O Error: 5". Hmm... Regards, Phil +----------------------------------+ | Phil Mayers, Network Support | | Centre for Computing Services | | Imperial College | +----------------------------------+ -----Original Message----- From: Evan Simpson [mailto:evan@4-am.com] Sent: 23 March 2001 16:00 To: Mayers, Philip J; zope@zope.org Subject: Re: [Zope] PythonScript editing time From: "Mayers, Philip J" <p.mayers@ic.ac.uk>
I've got a large-ish pythonscript that does some pretty ugly stuff - the application pattern requires it be a single script. Editing it (hitting Change on the TTW interface) takes a long (10sec-ish) time. Is this expected? Zope appears to peg the CPU at the same time...
How largish, exactly? A big enough script could certainly take a while to apply restrictions to, but I have to admit that I haven't benchmarked Script compilation. Cheers, Evan @ digicool & 4-am