Closed
Bug 92478
Opened 23 years ago
Closed 5 years ago
Rewrite nsXBLService::FetchBindingDocument so that it avoid copy
Categories
(Core :: XBL, defect)
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: dougt, Unassigned)
References
Details
(Keywords: perf)
Attachments
(1 file)
2.95 KB,
patch
|
Details | Diff | Splinter Review |
nsXBLService::FetchBindingDocument could use nsIInputStream::ReadSegments to
avoid copying. Currently it calls Read() which copies bytes into a local buffer.
Reporter | ||
Comment 1•23 years ago
|
||
Reporter | ||
Comment 2•23 years ago
|
||
Darin, can you review this?
Reporter | ||
Updated•23 years ago
|
Target Milestone: --- → mozilla0.9.4
Comment 4•23 years ago
|
||
The synchronous case in this function is almost never hit, so shouldn't make
much of a difference.
If you want to check it in, sr=hyatt.
Assignee: hyatt → dougt
Target Milestone: mozilla0.9.4 → Future
Comment 5•23 years ago
|
||
r/sr=darin
Comment 7•21 years ago
|
||
At this point we load the data using nsSyncLoadService::LoadLocalXBLDocument,
which wraps the raw stream in a buffered input stream and passes that to the
OnDataAvailable (the parser). I assume that this in fact does do an extra copy,
right?
Updated•15 years ago
|
QA Contact: jrgmorrison → xbl
Updated•15 years ago
|
Assignee: hyatt → nobody
Comment 8•5 years ago
|
||
XBL is now disabled in Firefox (Bug 1583314) and is in the process of being removed from Gecko (Bug 1566221), so closing bugs requesting changes to its implementation as wontfix.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Comment 9•5 years ago
|
||
This bug is flagged with "PERF" key word. Will taking out this code negatively affect the performance at all?
Comment 10•5 years ago
|
||
No. Now instead of running code that does a copy (which was bad for perf) we don't run that code at all.
You need to log in
before you can comment on or make changes to this bug.
Description
•