search for: ru_inblock

...write anything > for either backend. What exactly are the "In/Out" numbers? that's just the output from /usr/bin/time -f '%e\t%U\t%S\t%M\t%I/%O' The manual describes them as "number of file system inputs/outputs". From looking at the source, they correspond to ru_inblock and ru_oublock fields from the getrusage call. AFAIU, that means the number of non-cached read/writes. d

...r backend. What exactly are the "In/Out" numbers? > > that's just the output from /usr/bin/time -f '%e\t%U\t%S\t%M\t%I/%O' > > The manual describes them as "number of file system > inputs/outputs". From looking at the source, they correspond to > ru_inblock and ru_oublock fields from the getrusage call. AFAIU, that > means the number of non-cached read/writes. Non-cached reads/writes are arguably the most useful sort to measure, but the reads at least will be sensitive to OS caching, which means a repeat run will generally show lower numbers of re...

...hared memory size */ + __kernel_long_t ru_idrss; /* integral unshared data size */ + __kernel_long_t ru_isrss; /* integral unshared stack size */ + __kernel_long_t ru_minflt; /* page reclaims */ + __kernel_long_t ru_majflt; /* page faults */ + __kernel_long_t ru_nswap; /* swaps */ + __kernel_long_t ru_inblock; /* block input operations */ + __kernel_long_t ru_oublock; /* block output operations */ + __kernel_long_t ru_msgsnd; /* messages sent */ + __kernel_long_t ru_msgrcv; /* messages received */ + __kernel_long_t ru_nsignals; /* signals received */ + __kernel_long_t ru_nvcsw; /* voluntary context swit...

I hadn't noticed any interactive slowdown, but when I got around to running the notmuch performance suite, there seems to be some noticable slowdown with the glass backend (default in Xapian 1.3.5) compared to chert (using xapian 1.2.22) These tests are on an older i7 with 12G of RAM and an SSD. I'm reasonable confident they are CPU bound. One curious thing is the increase in system time