|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Victor Duchovni (Victor.Duchovni_at_morganstanley.com)
Date: Sat Nov 02 2002 - 11:50:21 CST
On Sat, 2 Nov 2002, Matthias Andree wrote:
> Another thing to mention is that the current version is Berkeley DB
> 4.1.24, with 6 additional patches filed, two or three of them might
> matter to Postfix installations.
>
Or one could upgrade from 4.1.17 to 2.7.7 :-) Actually I am curious about
the comment about buffer cache vs mmap for read-only databases. Can anyone
expand on what this means? Does Berkeley DB no longer use a fixed size
mpool for read-only databases? If so, there may finally be an incentive to
upgrade unless code bloat has once again trumped any improvements in the
latest release.
Does anyone have any measurements of memory utilization and
query latency as a function of "berkeley_db_read_buffer_size"? Presumably
if read-only databases no longer use an mpool, the read performance will
not depend on this parameter with 4.1.24 and could be better than read
performance with any version of Berkeley DB that does use its own
buffer-cache for read-only databases.
I suspect that many of the folks who care enough to do measurements have
already bolted to "cdb", but perhaps someone is still in a position to
run some meaningful tests. Is 4.1.24 faster for lookups on any platform
than 2.7.7?
-- Viktor.- To unsubscribe, send mail to majordomo
postfix.org with content (not subject): unsubscribe postfix-users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
postfix.org with content
(not subject): unsubscribe postfix-users