issue-8d7eb5e77b10907194dd621e37773b38706eef83.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: garbage collection performance tuning
desc: ""
type: :task
component: duk
release: v0.9
reporter: sva <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2013-12-10 23:56:41.037963 Z
references: []

id: 8d7eb5e77b10907194dd621e37773b38706eef83
log_events: 
- - 2013-12-10 23:56:41.197895 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-01-15 20:27:59.519529 Z
  - sva <sami.vaarala@iki.fi>
  - commented
  - |-
    Garbage collection period should be relative to current heap object count and string count,
    or perhaps a byte size estimate of these.  When reference counting is disabled, the interval
    computed from these must be much smaller.  Since the trigger counter is decremented on each
    allocation, object relative (rather than byte relative) trigger count is probably the most
    appropriate.
- - 2014-01-15 20:54:50.806188 Z
  - sva <sami.vaarala@iki.fi>
  - assigned to release v0.9 from v0.10
  - ""
- - 2014-01-15 20:54:55.062145 Z
  - sva <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - ""