Gregory Burd 1d6dfee192 Cache sizing is critical for performance. This change guesses at a ... reasonable setting for the WiredTiger cache size at runtime. This cache is shared across all vnodes regarless of how many are active at any given time. The algorithm is: max(1GB, 1/3 (RAM - Beam RSS size)). We don't enable direct_io on purpose and data will be double buffered in WiredTiger's cache and the filesystem buffer cache. This turns out to be faster than direct I/O despite wasting a bit of RAM.		2013-03-14 13:27:59 -04:00
..
riak_kv_wterl_backend.erl	Cache sizing is critical for performance. This change guesses at a	2013-03-14 13:27:59 -04:00
temp_riak_kv_backend.erl	Cache sizing is critical for performance. This change guesses at a	2013-03-14 13:27:59 -04:00
wterl.app.src	make wterl an app, cache the WT connection	2012-02-17 00:42:22 -05:00
wterl.erl	Start with a more rational default configuration. (Before you ask... the	2013-03-12 17:16:15 -04:00
wterl_app.erl	make wterl an app, cache the WT connection	2012-02-17 00:42:22 -05:00
wterl_conn.erl	allow WiredTiger config to be set in application env	2012-04-09 16:50:01 -04:00
wterl_ets.erl	add wterl_ets to hold ets table for wterl_conn	2012-04-05 16:10:50 -04:00
wterl_sup.erl	add wterl_ets to hold ets table for wterl_conn	2012-04-05 16:10:50 -04:00