Skip to content

Commit

Permalink
Config hash prop limit to 64
Browse files Browse the repository at this point in the history
  • Loading branch information
svaarala committed Jan 15, 2017
1 parent 07f8d68 commit c0f4a91
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion config/config-options/DUK_USE_HOBJECT_HASH_PROP_LIMIT.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
define: DUK_USE_HOBJECT_HASH_PROP_LIMIT
introduced: 2.1.0
default: 8
default: 64
tags:
- performance
- lowmemory
Expand All @@ -18,3 +18,11 @@ description: >
A lower value improves performance (a value as low a 4-8 can be useful)
while a higher value conserves memory.
The heap-wide object property slot cache accelerates repeated property
accesses to small and medium size objects with no upfront cost, so the
default limit has been raised to a relatively high value; the hash part
still makes sense for large objects where slot cache misses lead to very
large linear scans. The hash part also makes sense for long term objects
which are accessed often, e.g. prototype objects, but these's currently not
enough state to ensure they get and keep a hash part.

0 comments on commit c0f4a91

Please sign in to comment.