Comments on: Scaling Zend_Form http://matthewturland.com/2008/11/05/scaling-zend_form/ Mon, 23 Aug 2010 09:28:12 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Matthew Turland http://matthewturland.com/2008/11/05/scaling-zend_form/comment-page-1/#comment-252 Matthew Turland Thu, 09 Apr 2009 23:51:45 +0000 @till The referenced SVN changeset was in response to my finding regarding the translation bottleneck, but everything else I've described here is modifying Zend_Form behavior that exists by design. So, there aren't really any issues to report as this is the way that these components are intended to function and my use cases are for them are (apparently) unorthodox. @till The referenced SVN changeset was in response to my finding regarding the translation bottleneck, but everything else I’ve described here is modifying Zend_Form behavior that exists by design. So, there aren’t really any issues to report as this is the way that these components are intended to function and my use cases are for them are (apparently) unorthodox.

]]> By: till http://matthewturland.com/2008/11/05/scaling-zend_form/comment-page-1/#comment-251 till Thu, 09 Apr 2009 09:41:52 +0000 Interesting bits! :-) Did you open issues for your findings? E.g. disabling the translator? Interesting bits! :-) Did you open issues for your findings? E.g. disabling the translator?

]]> By: Matthew Turland http://matthewturland.com/2008/11/05/scaling-zend_form/comment-page-1/#comment-230 Matthew Turland Fri, 07 Nov 2008 00:39:14 +0000 Whether or not several smaller forms would work really depends on the requirements of the application. Dividing a form into subforms only works if you only display a subform worth of fields per page load and it's the obvious solution if that's conducive to fulfilling the requirements. Otherwise, dividing the form into subforms does nothing but add unnecessary overhead. The intent of this blog entry wasn't to suggest that either approach of having one larger form or several smaller forms is better than the other, but to describe how to modify Zend_Form such that it performs better in situations where the developer is forced by requirements to have one large form and some of the flexibility provided by Zend_Form is not necessarily needed. I personally used the approach I described with a form having over 250 fields and was able to reduce the page load time from 4.5 to 1.5 seconds. This still isn't an ideal request per second rating, obviously, but it's a significant improvement and I think it points to an area where Zend_Form could be improved as well. Whether or not several smaller forms would work really depends on the requirements of the application. Dividing a form into subforms only works if you only display a subform worth of fields per page load and it’s the obvious solution if that’s conducive to fulfilling the requirements. Otherwise, dividing the form into subforms does nothing but add unnecessary overhead.

The intent of this blog entry wasn’t to suggest that either approach of having one larger form or several smaller forms is better than the other, but to describe how to modify Zend_Form such that it performs better in situations where the developer is forced by requirements to have one large form and some of the flexibility provided by Zend_Form is not necessarily needed.

I personally used the approach I described with a form having over 250 fields and was able to reduce the page load time from 4.5 to 1.5 seconds. This still isn’t an ideal request per second rating, obviously, but it’s a significant improvement and I think it points to an area where Zend_Form could be improved as well.

]]> By: Jani Hartikainen http://matthewturland.com/2008/11/05/scaling-zend_form/comment-page-1/#comment-229 Jani Hartikainen Thu, 06 Nov 2008 23:07:50 +0000 An interesting approach, but personally I'd rather make a few small forms than a gargantuan 100-field one. For example, I'd hate to see the browser/os/something crash while filling that... An interesting approach, but personally I’d rather make a few small forms than a gargantuan 100-field one. For example, I’d hate to see the browser/os/something crash while filling that…

]]>