Bug #2424

Formbuilder has huge memory footprint

Details

Request #2424	Formbuilder has huge memory footprint
Submitted	2004-09-30 17:06 UTC
From	aaron at synthesyssolutions dot com
Status	No Feedback
Package	DB_DataObject_FormBuilder
PHP Version	4.3.9
OS	Slackware
Roadmaps	(Not assigned)

Comments

[2004-09-30 17:06 UTC] aaron at synthesyssolutions dot com

Description:
------------
I've been moving portions of a FOSS project (OpenIT) over to DataObjects & decided to take a crack at formbuilder. I converted a couple of the forms, then noticed something in our debugging info at the bottom. The new forms were taking as much as 3mb on the server to process. I went back to one of the simpler forms (Table: Campuses, Fields: ID (int), Description (varchar 50)), that only had one editable text field (description). That page reported that it was using 2200kb of ram. (Oddly enough on a more complex form, if I am creating a new record, it takes aprox 2800k & if I'm editing a record it jumps to about 3800k). The older pre- DO & formbuilder forms seem to stay at about 1300k.

I guess that in short, I'm wondering if there is any way to reduce that footprint without dropping formbuilder?

Reproduce code:
---------------
If there are problems reproducing this, I'd be happy to provide the source, though it appears to be completely independant of my code.

[2004-09-30 19:40 UTC] aaron at synthesyssolutions dot com

papercrane, you are probably correct, it probably isn't just formbuilder. Previously we'd just hand-coded all our forms in html, I may try a variation that is pregenerated & only uses quickforms to see which of the two is the bigger issue.

To get memory usage we call: memory_get_usage() which returns the amount of memory allocated to PHP. I'm doing all this development on a system that isn't getting any other webserver traffic.

When I get the chance I'll probably try the getForm() definition as well, and I'll post my results one way or another.
Thanks for the quick response guys!