Alexander Gorrod added a comment - Sep 04 2015 06:42:24 AM +00:00 For example, if I run an extended version of the wtperf parallel-populate-btree workload, gathering stats every 5 seconds I see: $ grep "in-memory page" WT_TEST/WiredTigerStat* Sep 04 16:31:25 81 WT_TEST cache: in-memory page splits Sep 04 16:31:25 497499 WT_TEST cache: in-memory page passed criteria to be split <snip> Sep 04 16:32:55 78 WT_TEST cache: in-memory page splits Sep 04 16:32:55 625 WT_TEST cache: in-memory page passed criteria to be split Sep 04 16:33:00 78 WT_TEST cache: in-memory page splits Sep 04 16:33:00 15055 WT_TEST cache: in-memory page passed criteria to be split The first occurrence is the most dramatic, but there are peaks later as well. i.e: In the first 5 seconds we returned true from can split over 6000 times per in-memory split.

Githook User added a comment - Sep 08 2015 12:15:58 AM +00:00 Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexg@wiredtiger.com'} Message: WT-2086 Add a statistic to track when can_evict sees splittable pages. Branch: develop https://github.com/wiredtiger/wiredtiger/commit/87078eb00a4053266b7efd472850b72bac3f6bf6

Githook User added a comment - Sep 08 2015 12:15:59 AM +00:00 Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'} Message: Merge pull request #2175 from wiredtiger/stat-splittable-pages WT-2086 Add a statistic to track when can_evict sees splittable pages. Branch: develop https://github.com/wiredtiger/wiredtiger/commit/39a69ec79cdb04e0f9286212e86d0c038db87b92