Re: Re: DB_DataObject performance

Does Propel support caching? Propel does not support caching of loaded objects. Torque does support caching through Manager classes, but these have not been included in Propel: it was felt that Managers would not add significant performance benefit in a PHP environment. Of course, you can always override methods like doSelect() in your Peer class to implement your own caching model. What is persistance then ? I currently using DBDO but ill check out what all the fuss is, and what is creole ? For website stuff i use MDB2 for the backend stuff i use DBDO. On 29/10/2005, at 12:30 PM, Dan Rossi wrote:

http://propel.phpdb.org/docs/user_guide/chapters/FindingObjects.html Does this mean it stores a serialized version of a class in the db ? Cant see the point, however their definition of a 'peristed' object is a little different to how its done say in a java application server ... On 29/10/2005, at 7:15 AM, Myke Hines wrote:

There was a good review of DB_DO, Propel and other object layer in php|architect (http://www.phparch.com/issuedata/articles/article_185.pdf) See Figure 2 for some specific numbers on how the three differ. I use propel and have good performance for a complete object layer (especially when your using an optimizer) On Oct 28, 2005, at 1:37 PM, Bertrand Mansion wrote:

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 -- PEAR General Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

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