Closed
Bug 501186
Opened 16 years ago
Closed 12 years ago
Profile object creation performance
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: dmandelin, Assigned: gal)
References
Details
Attachments
(2 files)
|
212 bytes,
application/x-javascript
|
Details | |
|
13.39 KB,
patch
|
Details | Diff | Splinter Review |
Results of attached test case:
run time (ms) empty loop run time (ms) cycles/obj alloc
js -j (TM) 1307 38 280
jsc (webkit) 497 32 86
v8 397 104 65
We are 3.3-4.3x slower at allocating new empty objects. Let's find out why and fix it.
Comment 1•16 years ago
|
||
See bug 501189 comment 1 et seq.
/be
| Assignee | ||
Updated•16 years ago
|
Assignee: general → gal
| Assignee | ||
Comment 2•16 years ago
|
||
I don't see any speedup from this. Maybe I am not measuring right though.
| Assignee | ||
Comment 3•16 years ago
|
||
Gregor, can you measure with this patch? If that moves the needle even a little, I can remove the other division too. I just want to make sure we are not chasing a ghost here.
Comment 4•16 years ago
|
||
I dont have the 1:1 mapping from source code to the disassembled instructions.
There is still one division left where we spend now 50% of the time in this function due to shark. Probably its the GC_FREELIST_INDEX macro.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•