Comments on: Zend_Db_Table time overhead – about 25%

By: Kevin H

Kevin H — Fri, 15 May 2009 17:11:59 +0000

Zend_Db_Table performance matters for small applications on shared hosting environments. Zend_Db_Table is horribly slow for most applications on a shared hosting environment. Simply put, 25% is the difference between usable and unusable.

Kevin

By: viperx

viperx — Fri, 17 Oct 2008 14:04:50 +0000

Hi fabrizio,
if you read the article you will see that I have included the case with metadata cache

By: fabrizio

fabrizio — Fri, 03 Oct 2008 15:20:05 +0000

What about using Zend_Db_Table_Abstract::setDefaultMetadataCache($cache);
as written in the reference guide?

” By default, Zend_Db_Table_Abstract queries the underlying database for table metadata upon instantiation of a table object. That is, when a new table object is created, the object’s default behavior is to fetch the table metadata from the database using the adapter’s describeTable() method.

In some circumstances, particularly when many table objects are instantiated against the same database table, querying the database for the table metadata for each instance may be undesirable from a performance standpoint. In such cases, users may benefit by caching the table metadata retrieved from the database.

There are two primary ways in which a user may take advantage of table metadata caching:

Call Zend_Db_Table_Abstract::setDefaultMetadataCache() – This allows a developer to once set the default cache object to be used for all table classes.
*

Configure Zend_Db_Table_Abstract::__construct() – This allows a developer to set the cache object to be used for a particular table class instance.
“

By: viperx

viperx — Thu, 18 Sep 2008 12:07:32 +0000

Ok Iczi, this is your point of view
And if your tareget is 2 or 3 servers OK, you are right. But if the application needs 100 servers then 20% is 20 more servers. Not that this is too much, but it is a difference indeed.

By: Iczi

Iczi — Tue, 16 Sep 2008 07:01:43 +0000

Well, Zend_Db_Table is “fast” enough for any website and any load. Today, developers like to scale PHP horizontally, means spreading your code to many servers and use a load-balancer to distribute the requests equally.

Even if Zend_Db_Table would add 50% overhead, that’s really no problem. Thanks to cheap servers!

I think, when talking about performance, we also have to think of “developer-performance”, means how fast a developer can finish his task. Developing and software-engineering are goind to be the most expensive parts of your projects, so it gets cheaper, if they are really fast and write mantainable and well tested code.

Zend_Db_Table provides tools to be faster, when it comes to solve database tasks and is a transparent and easy understable implementation.

So, who cares, if a PHP webapp can handle 150 or 200 request/s? I add a new server and then it’s going to be much faster than before and I saved time and/or money when i developed the application.

By: Zend_Db_Table erzeugt 25% Overhead sagt Andrei » Ralfs PHP und Zend Framework Blog

Thu, 28 Aug 2008 17:22:57 +0000

[...] Nikolov hat in seinem Blog einen Artikel über ein paar Performance-Messungen mit Zend_Db_Table veröffentlicht und kommt zu dem Schluss, dass Zend_Db_Table einen Overhead von bummelig 25% [...]