Re: DB_DataObject performance

Olivier Guilyardi wrote: >Hi, > >I've had successful experiences using DB_DataObject on corporate intranets, with >a few dozens of users. But I'm currently working on a website which may soon >receive about 30000 hits a day (latest evaluation). > >Have any of you already used DB_DataObject on high traffic websites ? >Is there any serious CPU and Memory usage benchmarks out there ? > >Here's the implementation choice I'm facing : >- either use DB_DataObject which relies on DB, DB_Result, etc... >- or code my own dataobjects which simply encapsulate mysql_* calls > >Wether I choose the first or second option, I'll stick with the "dataobject >design pattern" as a way to encapsulate the sql code and other smart behaviours. DB_DO should be ok for high traffic sites. The bottleneck comes from PEAR DB but it could be worse (for instance, Propel is not usable without a compiler cache). CRTX_DB is certainly faster as it uses PDO. That is if you use PHP 5 and live on the edge. My experiences with PDO show that it is not as stable and consistent as it should be... There is also my own solution, Phreez, but I am writing a lot of unit tests right now and it is not ready for primetime. Good luck, -- Bertrand Mansion http://www.mamasam.com - creative internet solutions http://golgote.freeflux.net - my blog