Closed
Bug 656347
Opened 15 years ago
Closed 12 years ago
Slashdot sluggishness and other issues
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tech Evangelism Graveyard
English US
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: azakai, Unassigned)
References
()
Details
In bug 654028 we saw that Slashdot is written in a way that performs poorly on Firefox. The main issue is running a large amount of JavaScript on *every* keypress (both text entry and scrolling), which generates a lot of collectible garbage. It is likely that only a browser with a generational GC would perform well on such code, which means just Chrome.
(Bug 654028 deals with our not collecting the garbage later. But the fact the garbage is even created, and so quickly, is something that the Slashdot JS could do much more efficiently.)
Additional issues exist with Slashdot such as bug 648278, leading to an overall poor experience for Firefox users on Slashdot. Perhaps it is not a coincidence, then, that Firefox is unpopular there, judging by user comments.
| Reporter | ||
Updated•15 years ago
|
URL: http://slashdot.org/
Comment 1•14 years ago
|
||
Please bump this up to a high priority performance issue.
The affect in this site is a symptom of a larger problem. By matching the performance of chrome here, it's likely an across the board performance increase will result, which will ensure gecko remains a viable mainstream platform.
| Reporter | ||
Comment 2•14 years ago
|
||
The underlying issue is already a very high priority. Slashdot can only be fast with a generational GC, and the JS team has that as one of their top goals, it in progress.
Comment 3•12 years ago
|
||
I'm not noticing any real issues with the site at this point. Seems to run fine. If the issue still exists please reopen and leave more details for the site to be contacted.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•11 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•