Closed
Bug 782694
Opened 12 years ago
Closed 12 years ago
Set GC parameters for otoro
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gwagner, Assigned: gwagner)
Details
Attachments
(1 file)
|
1.19 KB,
patch
|
cjones
:
review+
|
Details | Diff | Splinter Review |
We have 128MB RAM and child processed get killed with around 36MB. We should set the GC parameters to have more allocation based GCs.
|
Assignee | |
Comment 1•12 years ago
|
||
|
|
Assignee | |
Comment 2•12 years ago
|
||
With the new parameters we have
Heap growth based on heap size new vs. old
If GC is triggered every sec:
< 10MB -> 300% vs. 300%
10 - 40-> linear from 120 - 101% vs. linear from 300 to 150%
> 10MB -> 101% vs. 150%
If GC is triggered > 1 sec:
105% vs. 150%
Malloc based trigger
16MB vs. 128MB
|
|
Assignee | |
Updated•12 years ago
|
Attachment #651815 -
Flags: review?(jones.chris.g)
Comment on attachment 651815 [details] [diff] [review]
patch
Seems as good as anything else until we have decent benchmarks to test against ;).
Attachment #651815 -
Flags: review?(jones.chris.g) → review+
|
|
Assignee | |
Comment 4•12 years ago
|
||
|
||
Comment 5•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
•