Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We need to review the performance of this module when used in views with a large number of fields (let's say 20 rows with 3 fields each), and come up with clean solutions for this.
Comments
Comment #1
rjbrown99 CreditAttribution: rjbrown99 commentedFWIW, I'm using D6 with the DHTML widget in views and it works quite well. We're using it similar to how you have described it, but it's more like 100 rows with 3 fields each. The DHTML widget was the key.
Comment #2
lunk rat CreditAttribution: lunk rat commentedI am also seeing large performance overhead with my views, which have 100 rows with 4 fields each. click-to-edit is the only way to get the view to load without forcing my CPU fan into overdrive ;)
I see the worst CPU usage when scrolling views that have editable HTML or AJAX fields.
Comment #3
wizonesolutionsEven with click-to-load and 3 fields utilizing this (no pager, about 108 rows), I'm seeing a performance overhead that nearly doubles my page load time (according to XHProf). It's a bit over 7s for the view without any Editable formatters and nearly 13s with them.
Comment #4
Sinan Erdem CreditAttribution: Sinan Erdem commentedI have a table with aprox. 100 rows and 5 editable fields. Here are the views performance results:
Query build time 34.55 ms
Query execute time 5.63 ms
View render time 5612 ms
Render time is very high. Currently this table is not workable. Maybe a global button to enable or disable editable fields can be the solution.
Comment #5
Sinan Erdem CreditAttribution: Sinan Erdem commentedAlso with the above table, after displaying the table, each change on a cell takes about 6-7 seconds.
Comment #6
Renee S CreditAttribution: Renee S commentedAs an update, I'm still seeing this performance degradation in the newest versions of the module. 6-7 seconds, huge render times.
Comment #7
Renee S CreditAttribution: Renee S commentedSome stats on the current version:
Query build time: 13.65ms
Query execute time: 3.24ms
View render time: 5986.26ms
(eta: per-cell edit performance after the view loads is just as bad.)
Comment #8
Renee S CreditAttribution: Renee S commentedWe're willing to offer a bounty to smack down some performance improvements on this. Any takers? :)
Comment #9
ledom CreditAttribution: ledom commentedPerformance upgrade would be fine.
Drupal is missing a good way to make editable view with lots of row.
Editable views is saving all node one by one even with only one field updated (unusable with big views)
Slickgrid seems abandonned