diff options
author | 2014-04-11 15:46:52 +0000 | |
---|---|---|
committer | 2014-04-11 15:46:52 +0000 | |
commit | 942615efa992545faa398298d17b66a1c46b5500 (patch) | |
tree | e6872639f4715e9faa5f3fd4b577f6cbf14b8346 /arch.in | |
parent | 27c8079fded40c4d4345acd5aee489d29bb14470 (diff) | |
download | mandoc-942615efa992545faa398298d17b66a1c46b5500.tar.gz mandoc-942615efa992545faa398298d17b66a1c46b5500.tar.zst mandoc-942615efa992545faa398298d17b66a1c46b5500.zip |
Further apropos(1) speed optimization was trickier than anticipated.
Contrary to what i initially thought, almost all time is now spent
inside sqlite3(3) routines, and i found no easy way calling less of them.
However, sqlite(3) spends substantial time in malloc(3), and even more
(twice that) in its immediate malloc wrapper, sqlite3MemMalloc(),
keeping track of all individual malloc chunk sizes. Typically about
90% of the malloced memory is used for purposes of the pagecache.
By providing an mmap(3) MAP_ANON SQLITE_CONFIG_PAGECACHE, execution
time decreases by 20-25% for simple (Nd and/or Nm) queries, 10-20% for
non-NAME queries, and even apropos(1) resident memory size as reported
by top(1) decreases by 20% for simple and by 60% for non-NAME queries.
The new function, mansearch_setup(), spends no measurable time.
The pagesize chosen is optimal:
* Substantially smaller pages yield no gain at all.
* Larger pages provide no additional benefit and just waste memory.
The chosen number of pages in the cache is a compromise:
* For simple queries, a handful of pages would suffice to get the full
speed effect, at an apropos(1) resident memory size of about 2.0 MB.
* For non-NAME queries, a large pagecache with 2k pages (2.5 MB) might
gain a few more percent in speed, but at the expense of doubling the
apropos(1) resident memory size for *all* queries.
* The chosen number of 256 pages (330 kB) allows nearly full speed gain
for all queries at the price of a 15% resident memory size increase.
Diffstat (limited to 'arch.in')
0 files changed, 0 insertions, 0 deletions