Measurements show that this accounts for many cache misses.
SS scores don't change much. For a benchmark I create a linked list with 1000000 objects. I measure the time[ms] to 1) create the list 2) GC on whole list 3) delete root and GC On trunk I get: 40, 87, 49 with this patch: 37, 77, 45
Nick do you have a way to measure cache performance with this patch?
How does it affect our V8 score? If you're in Linux, an easy way to measure cache misses is with the perf tool. In Ubuntu, it's in the linux-tools-common package. Just run: perf stat ./js ... and it will print a summary of cache stuff after the command finishes.
(In reply to comment #3) > Nick do you have a way to measure cache performance with this patch? Yes. For what workload?
(In reply to comment #5) > (In reply to comment #3) > > Nick do you have a way to measure cache performance with this patch? > > Yes. For what workload? SS, V8 and maybe an allocation heavy page in the browser? Bill: I saw better scores for V8 in the browser but I still have to verify that this wasn't just noise. Haven't tried with the shell.
Created attachment 516165 [details] [diff] [review] patch
Attachment #516090 - Attachment is obsolete: true
I tried SS and V8 in the shell, the changes all looked like noise. I didn't try in the browser because those results tend to be much less deterministic and so very difficult to detect any meaningful difference that isn't large.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.