Closed Bug 936789 Opened 12 years ago Closed 12 years ago

Faster CC logger

Categories

(Core :: XPCOM, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla28

People

(Reporter: smaug, Assigned: smaug)

Details

Attachments

(3 files)

This makes the logger a lot faster, so I can just process all the data in browser. (nsTArray ended up doing memcpy all the time)
Attachment #829739 - Flags: review?(continuation)
Comment on attachment 829739 [details] [diff] [review] faster_cc_log.diff Review of attachment 829739 [details] [diff] [review]: ----------------------------------------------------------------- It would be handy to have a segmented array data structure in Gecko. Hopefully this won't increase memory usage too much on mobile.
Attachment #829739 - Flags: review?(continuation) → review+
Yeah, we need some kind of nsTBigArray, which doesn't promise continues memory location for indexes. Do we run CC logger on mobile, I mean the API which is used in JS. The patch doesn't affect to creating CC graph files.
On desktop CCGraph describers don't take too much memory comparing to the JS stuff needed to actually analyze the graph.
(In reply to Olli Pettay [:smaug] from comment #2) > Do we run CC logger on mobile, I mean the API which is used in JS. > The patch doesn't affect to creating CC graph files. Ah, right! Yeah, we just use the file dumping for B2G. So, we should be okay. > Yeah, we need some kind of nsTBigArray, which doesn't promise continues memory location for indexes. I've long considered generalizing the EdgePool data structure, but I've been too lazy to actually do it.
Attached patch v2Splinter Review
nsSegmentedBuffer exists, and might be what you're looking for.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla28
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: