so I wonder, will skiplist be a better choice? obviously running
quota(8) will be a very cheap operation, but I'm worried about
contention on the quota database during delivery etc. (these users are
for the most part not actively using the system -- they get less than
one message per day
Rob Mueller wrote:
so I wonder, will skiplist be a better choice? obviously running
quota(8) will be a very cheap operation, but I'm worried about
contention on the quota database during delivery etc. (these users are
for the most part not actively using the system -- they get less than
one
On Fri, 2007-01-19 at 21:58 +1100, Rob Mueller wrote:
What filesystem are you using? Have you considered trying reiserfs with
tails enabled. It's quite impressive how little disk space it actually uses
(don't believe du output). We used to use NVRAM cards, and even with 100,000
users, it
On Fri, 2007-01-19 at 07:49 -0500, Ken Murchison wrote:
Rob Mueller wrote:
The problem I saw was that accessing a skiplist db involves locking the
entire file I believe. This felt like a huge point of contention,
especially since every email delivered would lock it. I never did end up
[EMAIL PROTECTED]; info-cyrus@lists.andrew.cmu.edu
Sent: 1/19/07 9:42 AM
Subject: Re: using skiplist for quotas.db
On Fri, 2007-01-19 at 07:49 -0500, Ken Murchison wrote:
Rob Mueller wrote:
The problem I saw was that accessing a skiplist db involves locking the
entire file I believe. This felt
