From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: SQLite Clarification Date: Mon, 31 Jul 2006 17:13:57 -0400 Message-ID: <200607311713.57472.sgrubb@redhat.com> References: <20060731171437.GA447@clif.cflynt.com> <20060731200523.GA1183@clif.cflynt.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20060731200523.GA1183@clif.cflynt.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Clif Flynt Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Monday 31 July 2006 16:05, Clif Flynt wrote: > > The database file is only locked for the duration > > of the write operation - not while the database is open. =A0A write > > normally takes a few milliseconds, then the lock goes away. The issue here is that you may need write to have priority since there is= =20 potentially a backlog building in the kernel. If the backlog gets too big= you=20 will get a panic. The write operation has to be fast. But suppose there are readers. Does the write block or fail? More of a=20 curiosity to me. > > Why is 256 bytes of data for each 1MiB of database a problem? > > Is memory so short and databases so large that this might cause > > a problem? Database could be huge. A paranoid admin could easily get gigabytes of da= ta in=20 a short time. Or maybe someone that wrote a rule that captures too much d= ata=20 could run into a problem. > > If it is, then increase the page size from the default 1K. > > The actually usage is 2 bits per page of data. =A0So if pages > > are 32KiB bytes instead of 1KiB, a 1MiB database only needs > > 8 bytes of storage for the bitmap. This is good to know. That would probably help. -Steve