On Fri, 10 Feb 2006 10:32:40 +0000, Paul Johnston wrote:
Hi Paul
> Any obvious optimisations for cgiapp? Any obvious places I should
> check?
Dan Horne and others have pointed you to the Cache::* module, which I too
recommend. But even then there are things to watch out for:
o By tracing through my code (by reading it!) I found I was sometimes querying
the database more than once for the same data. The data structures were complex
- staff and their telephone services in a uni dept - where staff can have more
than 1 position, and each position can have more than 1 phone, and people can
share positions and phones (whew), so I started caching, and all was good...
o Until I started displaying stale data occasionally, and that was because it's
a major task to ensure the cache is invalidated at the correct times, so a query
really does go to the db and not the cache when the data has, or may have,
changed.
--
Cheers
Ron Savage, suppressed on 11/02/2006
http://savage.net.au/index.html
Let the record show: Microsoft is not an Australian company
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.