[Date Prev][Date Next] [Chronological] [Thread] [Top]

ldbm writesync

Just a suggestion, on the topic of cache flushing and such... In the
interest of speeding up bulk write operations:
	perform ldbm_open without writesync
	keep track of a "dirty" flag
	on *read* operations check for dirty, and perform an explicit
The ldbm_sync can be invoked after the read results are sent back to the
client, to avoid making the reader wait around. In the worst case of a very
active directory with lots of writes & reads, this should be no worse than
before. In the case of a major series of updates, this should be a bit
faster. For the paranoid, you can always issue a search after a write to
force a flush. Comments? (Other than "you've stayed awake too late again,