Closed Bug 1138151 Opened 9 years ago Closed 2 years ago

Scrolling on some specific pages causes Firefox to use HDD constantly and loudly

Categories

(Toolkit :: Places, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 661590
Performance Impact low

People

(Reporter: Virtual, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug, )

Details

(4 keywords, Whiteboard: [fxperf:p3])

Attachments

(1 file)

1. Open this URL website page - http://pubchem.ncbi.nlm.nih.gov/compound/656612?from=summary#section=Top
2. Scroll page to the bottom and next to the top a few times
3. You can clearly hear that your HDD is used loudly and constantly by Firefox



The issue doesn't occur in in:
-Chrome (Blink engine),
-Opera (Blink engine),
-Opera (Presto engine) [poor scrolling performance];
but Vivaldi (Blink engine) is also affected.
possible testcase.
Component: Untriaged → Places
Product: Firefox → Toolkit
I see lots of disk usage. But it doesn't majorly affect scroll speed, so how is this topperf?
Also occurs on http://rr-project.org/rr.html#1.0 .  As soon as a page is scrolled, Nightly writes to the disk. Quickly scrolling the pages will peg the HDD constantly
the testcase is not very common, so not a priority, but still worth investigating.
Unfortunately the regression range is not really useful, too old and widespread.
Chrome is storing history for each fragment, as we do, in a similar table, so the disk load should be ideally similar.

First thing to notice from the log, we seem to read the page info twice (double calls to FetchPageInfo), likely one can be avoided (to be verified).
Then we fetch the visit id, the only reason is to notify onVisit, but it's unlikely a useful information, we we could stop notifying that and save a read.
Then we update Frecency for the url, this is expensive, we could evaluate some way to delay it so that we do only if a further visit to the same page is not seen in a timeframe (so we don't update too often).

So, there is definitely some space for improvements, but globally I think most of the churn here comes from keeping frecency updated.
Blocks: PlacesJank
Flags: needinfo?(mak77)
Keywords: topperf
Depends on: 1209027
Priority: -- → P5
Whiteboard: [qf:p1]
Whiteboard: [qf:p1] → [qf]
Whiteboard: [qf] → [qf:investigate:p1]
Maybe my profile will has some hint and speed up diagnosing & investigating this issue.

Profile: https://perfht.ml/2opHq6q
Taken with: Gecko Profiler 2.1.0
Interval: 0,01 ms
Buffer size: 900 MB
Threads: ,
Features: Stack walk + JavaScript + Task tracer
Whiteboard: [qf:investigate:p1] → [QRC][QRC_NeedAnalysis][qf:investigate:p1]
Whiteboard: [QRC][QRC_NeedAnalysis][qf:investigate:p1] → [qf:p3]

Since this bug is not a high priority, a regression, or a security issue, it's not necessary to track its status.

It is the regression (please see the keywords), but very long standing one.

QA Contact: Virtual
Blocks: 1594504
See Also: 1594504
Priority: P5 → P3
Depends on: 1598187
OS: Windows 7 → All
See Also: → 1419053
Whiteboard: [qf:p3] → [qf:p3] [fxperf:p3]

Google Maps is also affected when zooming and panning.

See Also: → 1722313
See Also: 1722313
See Also: → 1722313

I've simply moved my Firefox profile to a RAM disk.

The application really wants to destroy my SSD disk (and that is despite browser.cache.disk.enable=0).

Performance Impact: --- → P3
Whiteboard: [qf:p3] [fxperf:p3] → [fxperf:p3]
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: