hello

i have a somewhat larger base of Nody Types (11), Fields (11 custom) and ImageCache presets (~120).
everything is fine... until i enable this module.

what was once a 512KB 'dpl_content_node_field_instance' table, turns into 1.5MB once i setup the display order for JUST the cck Basic order of JUST a content type.

i discovered that the more i edit, the bigger it equally gets.
upon editing the last of the 11 content types, on the two last cck display order, the system would no longer respond - each request to edit the ordering would fail with lack of memory, each request to process ANY page would take an incredible amount of time.

just for the record, i was registering 460MB memory usage on apache, plus 60MB for APC, and the CPU was always under heavy load, starting at 60% and then jumping to 100%, something i never saw on this VPS from Linode. as for the table, it was huge! 12+MB. so basically, you can't dream about this module scaling, at all.

then i had the brilliant idea of uninstalling the module, but tada, it DOES NOT erase its remains in the DB, so the table remained the same and i had to redo the fields.

long story short, your module caused my a huge headache and 1 full night of work lost between diagnosing, work, gray hairs, etc) and a boss upset with me.

now to be more constructive... is there any way this module can be recoded to not behave this way, please?
the way it is, it is even __hardly__ of any use for small setups, because it's just too much overload.

and please add a routine to get rid of the remains from the 'dpl_content_node_field_instance' table.

CommentFileSizeAuthor
#2 sample_sql.txt30.71 KBlpalgarvio

Comments

lpalgarvio’s picture

sample SQL export of just 1 ordering done for just 1 content type.

edit, nevermind, ill upload instead.

lpalgarvio’s picture

StatusFileSize
new30.71 KB

sample SQL.

60+% of it is just gibberish introduced by content display order.

by the way, it seems it does not like much when we rename content types or delete/add fields.

lpalgarvio’s picture