PHP Pear - Re: [PEAR] Re: [PEAR-DEV] DB

Author

Re: [PEAR] Re: [PEAR-DEV] DB_DataObject performance

Myke Hines

2005-10-28, 6:58 pm

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:
>
>
> with
>
> 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
>
>

Olivier Guilyardi

2005-10-28, 6:58 pm

Myke Hines wrote:
> There was a good review of DB_DO, Propel and other object layer in
> php|architect (http://www.phparch.com/issuedata/ar...article_185.pdf)

Very interesting

> 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)

Actually I was so much worried about memory and cpu usage that I forgot the
number of SQL queries... Thanks to remind me that.

Looks like I should take a further look to Propel and EZPDO. Even if I end up
not using them, their design patterns and strategies may be great sources of
inspiration.

Thanks

--
og

Dan Rossi

2005-10-28, 9:56 pm

http://propel.phpdb.org/docs/user_g...ingObjects.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/ar...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:
>
>

Dan Rossi

2005-10-28, 9:56 pm

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

Sponsored Links