Hi,

Having spent a little time on Google (and reading unrelated articles ...) I
would like post my question here again (as advice on the list is always very
valuable indeed!): 

Q: What would be the best way to save db calls for large result sets? 

I thought about serializing the data and then caching it (with Cache_Lite -
maybe there will be a future inclusion of such a caching scheme into the php
core or pecl?). I was not sure about performance though (no time for
benchmarking this).

The issue is that as this system grows we get 2 - 3 db calls on the server
(which is too much in my opinion), but will serializing be cheaper or simply
the lesser of two evils?

Thanks already (as top posting is a sin) for your replies ...

T


SPIRAL EYE STUDIOS 
P.O. Box 37907, Faerie Glen, 0043

Tel: +27 12 362 3486
Fax: +27 12 362 3493 
Mobile: +27 82 442 9228
Email: [EMAIL PROTECTED]
Web: www.spiraleye.co.za 

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to