On 23/07/13 15:23, Erik Moeller wrote:
Editing this page in Firefox on a 6-year-old system
only slightly
faster than the tester's specs today takes about 5 seconds to
initialize. In Chrome it takes about 3 seconds, in the ballpark of
reloading the page into the source editor. Note that Gabriel put major
caching improvements into production around June 7, which may not have
been in effect for this user / this page yet.
I tried editing [[Argentina]] on my laptop just now, it took 45
seconds of CPU time and 51 seconds of wall clock time before the
percentage CPU usage began to drop. It's pretty slow.
Still, I think that the hypothesis that any actual
negative impact of
VE on new users is due to performance issues is very supportable.
Performance is the single biggest issue overall for VE right now, and
performance on long pages can absolutely be prohibitively poor.
Improving it is the highest priority for the team.
Is there any estimate as to how much development time it might take to
improve performance by an order of magnitude or so, as seems to be
required?
-- Tim Starling