This message was deleted.
# general
s
This message was deleted.
c
can you check if you are page faulting a lot?
k
@churro, do you mean that if the memory is not enough large for all the mapped segment files (or put another way, all the files are mapped to the historical process) we start to see "thrashing" of paging in and paging out?
c
i think the historicals download the active segments and mmap all of them, whether they are queried or not. So the OS decides which pages get cached….so i would imagine if you see a lot of page faulting, you need to adjust your memory to disk ratio.
k
thx, that is what I suspect. It would be great if you can share some code pointers.
@churro, It took me some time to find the pgmajfault statistics. It actually turned out the why the
query/segment/time
is high, the page fault seems to be low. Though now that well correlated. Does this point to other forces that cause the query/segment/time to be high?
This is query/segment/time
and this is the pgmajfault avg over all historicals: