I was looking at some statistics via the wtstats graph tool, and they don't appear to match those in the original file.
The two statistics are:
tracked dirty bytes in the cache
and
bytes currently in the cache
The wtstats graph I see for those two statistics is:
An extract of the raw data is:
Mar 10 06:00:07 13937645434 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:00:07 15032413045 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:00:17 14118949794 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:00:17 15031434886 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:00:27 14245210823 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:00:27 15032327122 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:00:37 13829546010 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:00:37 14839582962 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:00:47 13598968927 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:00:47 15030610981 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:00:57 13407003442 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:00:57 15032283870 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:01:07 14325052454 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:01:07 15031068774 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:01:17 14373973388 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:01:17 15031787034 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:01:27 14959868383 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:01:27 15032397299 /mnt/fast/alexg/data cache: bytes currently in the cache -- Mar 10 06:01:37 14865619787 /mnt/fast/alexg/data cache: tracked dirty bytes in the cache Mar 10 06:01:37 15032398484 /mnt/fast/alexg/data cache: bytes currently in the cache
I wonder whether the tool is treating the tracked dirty bytes as a running total rather than an absolute number?
- is depended on by
-
SERVER-18199 WiredTiger changes for MongoDB 3.1.2
-
- Closed
-