Posted by Damien Tournoud on July 3, 2011 at 9:36am
4 followers
Jump to:
| Project: | editablefields |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
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
#1
FWIW, 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.
#2
I 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.
#3
Even 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.