Good news is that Speedy did increase the speed a bit. However, I am experiencing some strange effects. Changes I make to the MySQL server are not taking effect until I either kill all the Speedy_backend processes or I reboot the server, in my case the reboot is faster.

Am I right in the assumption that the speedy backend is keeping things in memory, thus my changes are not taking place? If this is the case, a way of enabling and disabling speedy would be nice. That way a user can use the perl implementation during development and then once all the bugs are out turn speedy on.

Wil

Think of Speedy as a big cache for cgi scripts. I think the expire on it is about 300, so processes do die off and get replaced in time.

I'm not sure what the 'restart' is, but you might want to check the full docs.

I'm running in a development environment, and had to kill all those features to prevent "historical innacuracies" from driving me crazy <G>

PUGDOG®
PUGDOG® Enterprises, Inc.
FAQ: http://pugdog.com/FAQ

Exactly my problem....... But it is gone now. I made a list of files that used speedy so that once development is over I can change them back.

What would be really nice is if in setup there was a check box for update cgi files, so that if you change the perl string from /usr/local/bin/speedy to /usr/local/bin/perl and have the check box checked it would update all the cgi files. Hopefully Alex will put that one on the wish list.

Wil

Hi,

Can you expand on "Changes I make to the MySQL server are not taking effect". What changes did you make exactly? You should be able to update your config files, or change your data structures under SpeedyCGI and not reset the speedy_backend.

Cheers,

Alex

--
Gossamer Threads Inc.