Performance problems with large quantities of content

[GoogleCodeExporter]

When given a large quantity of HTML, Loki starts to get very sluggish and 
unresponsive.

The attached document was quite effective at getting Loki to be poky.

Original issue reported on code.google.com by matt.d.r...@gmail.com on 25 Mar 2008 at 9:05

Attachments:

• long_content.html

[GoogleCodeExporter]

It looks like making changes to this document sets off a very large (if not 
infinite)
flurry of cleanup calls, on account of the Firefox 2 auto cleanup on paste 
kludge.

Obviously, this should not be happening.

Original comment by enaes...@gmail.com on 30 Jun 2008 at 2:57

• Added labels: Component-Cleanup, Milestone-Release2.0, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I added a trap in r366 that seems to be preventing the infinite loop (which was 
being
caused by the auto-cleanup triggering other auto-cleanups).

But there is still a noticeable delay as you start typing. This is because the 
code
watches for node insertions, and begins a cleanup once it sees that no further 
nodes
have been added in the last 0.15 seconds. If you are typing in a new paragraph, 
after
the first character you are no longer adding other nodes, and the cleanup runs 
after
only a few letters have been entered. Performance is restored later, after the
cleanup finishes.

Original comment by enaes...@gmail.com on 30 Jun 2008 at 3:17

• Changed state: Started

[GoogleCodeExporter]

As of r371, I've killed off the old system of trapping pastes based on node 
insertion
events. Instead, Loki now looks for the paste keyboard shortcut and runs a 
cleanup
after that. This opens up a deficiency (issue 89), but one that I think is 
minor.

Loki (on the webdev iMac) no longer struggles with the long_content document at 
all.

Original comment by enaes...@gmail.com on 30 Jun 2008 at 5:33

• Changed state: Fixed
• Added labels: Fixed-2.0rc4