Open Bug 1246969 Opened 10 years ago Updated 5 years ago

nsIBufferedStreams implementation inflates (measured?) IO

Categories

(Core :: Networking: File, enhancement, P5)

Product:
Core
Component:
Networking: File
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox47 --- affected

People

(Reporter: gcp, Unassigned)

References

Details

(Whiteboard: [necko-backlog])

Background story in bug https://bugzilla.mozilla.org/show_bug.cgi?id=1244259. https://bugzilla.mozilla.org/show_bug.cgi?id=1244259#c12 https://bugzilla.mozilla.org/show_bug.cgi?id=1244259#c37 https://bugzilla.mozilla.org/show_bug.cgi?id=1244259#c40 This seems to be caused by bug 1211090. Introducing BufferedInputStream and BufferedOutputStream with a 64k buffer has made the measured IO of writing a 16 byte file go up to 64k. Is this an issue with xpref? Is there something fishy with the BufferedStream implementation? Did we miss something in the SafeBrowsing code/fallocate changes? This was all measured on Windows 7.
Blocks: 1244259
There's a mitigation in place by making sure the buffer size <= file size, so this isn't very urgent to fix.
Severity: normal → enhancement
Whiteboard: [necko-backlog]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.