Last modified: 2014-03-11 02:04:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55825, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53825 - VisualEditor: Reduce memory usage
VisualEditor: Reduce memory usage
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
Data Model (Other open bugs)
unspecified
All All
: High enhancement
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks: ve-performance
  Show dependency treegraph
 
Reported: 2013-09-05 20:01 UTC by Brion Vibber
Modified: 2014-03-11 02:04 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Brion Vibber 2013-09-05 20:01:42 UTC
Editing of large pages can use a significant amount of memory; a spotcheck that Max did on [[United States]] showed an increase of 121MB usage in Chrome while editing the page.

This is a concern for us for mobile in particular, as today's mobile devices have the amount of memory of computers from several years ago -- most have 1GB or 512MB (or even less), which has to house the operating system, background apps, the web browser, and the *entire* article with a richly annotated DOM.

Possible techniques for reducing memory usage were proposed at the VE mobile meeting yesterday:

* Section editing -- if we only have to load up a single section at a time, large pages won't use up nearly as much memory. Note that on mobile we already divide the page up into sections surrounded by <div>s that can be replaced with the editable surface; the other sections on page might not even be open.

* Limit full annotation processing to areas under active editing -- apparently it should be possible to delay some of the HTML processing on sections or even paragraphs that have not yet been edited. This might also save memory, but needs to be looked into.
Comment 1 James Forrester 2013-09-05 20:57:22 UTC
Not sure this is a Mobile-specific bug, but yes, very important to make progress here. I think there's likely to be some produce trade-offs that are more appropriate for the Mobile than Desktop experience, though, so certainly some of it will be…
Comment 2 Brion Vibber 2013-09-05 21:10:57 UTC
Feel free to move this to 'general' and we'll hang some mobile-specific bugs off it that are more directly actionable.
Comment 3 James Forrester 2013-09-05 21:24:24 UTC
(In reply to comment #2)
> Feel free to move this to 'general' and we'll hang some mobile-specific bugs
> off it that are more directly actionable.

{{Done}}

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links