On Thu, Jul 24, 2008 at 1:08 PM, Mike Cochrane <[EMAIL PROTECTED]> wrote: > Alexey Zakhlestin wrote: >> >> memcache shouldn't be the only option. it should be possible to also >> use apc/xcache shared-memory caches — they would be more suitable for >> small (1000 users) installations. >> >> Anyway, I usually add caches using the following scenario: >> 1) Profile app using XDebug >> 2) Analyze bottlenecks >> 3) Optimize code and/or sql >> 4) Profile again >> 5) If there is no any meaningful optimization left, introduce >> appropriate caching >> > > Me too :-) I'm at 1/2/3 at the moment. I don't know how I lived without > XDebug. > > Thanks I hadn't considered the other shared memory caches. I'll allow for > them. I guess the consideration for me at the moment is whether to cache the > objects or cache the results of the query and create the object again. I'd > rather cache the smallest useful amount of info (the db row) instead of the > object but DB_DataObject doesn't initially look like it's going to make that > easy.
Well, I guess the decision will come naturally after profiling cycles. Probably some pre-generated pages would fit nice into cache and some user-data too.. It's too early to plan now -- Alexey Zakhlestin http://blog.milkfarmsoft.com/ _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
