Review the performance of views with a large number of editablefields and come up with solutions

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.

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.

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.

I 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.

Also with the above table, after displaying the table, each change on a cell takes about 6-7 seconds.

As an update, I'm still seeing this performance degradation in the newest versions of the module. 6-7 seconds, huge render times.

Some 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.)

We're willing to offer a bounty to smack down some performance improvements on this. Any takers? :)

Performance 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