Estimate a reasonable cache size if one isn't provided in app/env config for wterl. #5

Merged
gburd merged 1 commit from gsb-cache-size-est into master 2013-03-14 18:05:38 +00:00
gburd commented 2013-03-14 17:35:17 +00:00 (Migrated from github.com)

This change guesses at a reasonable setting for the WiredTiger cache size at runtime. This cache is shared across all vnodes regardless 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.

This change guesses at a reasonable setting for the WiredTiger cache size at runtime. This cache is shared across all vnodes regardless 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.
vinoski commented 2013-03-14 18:05:34 +00:00 (Migrated from github.com)

+1

+1
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: greg/wterl#5
No description provided.