From c0f4a9180aabce35ffe8ec10952618d68c568553 Mon Sep 17 00:00:00 2001 From: Sami Vaarala Date: Sun, 15 Jan 2017 04:30:34 +0200 Subject: [PATCH] Config hash prop limit to 64 --- .../DUK_USE_HOBJECT_HASH_PROP_LIMIT.yaml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/config/config-options/DUK_USE_HOBJECT_HASH_PROP_LIMIT.yaml b/config/config-options/DUK_USE_HOBJECT_HASH_PROP_LIMIT.yaml index 008b836180..bea59096e3 100644 --- a/config/config-options/DUK_USE_HOBJECT_HASH_PROP_LIMIT.yaml +++ b/config/config-options/DUK_USE_HOBJECT_HASH_PROP_LIMIT.yaml @@ -1,6 +1,6 @@ define: DUK_USE_HOBJECT_HASH_PROP_LIMIT introduced: 2.1.0 -default: 8 +default: 64 tags: - performance - lowmemory @@ -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.