Re: Single Transaction stores complete database

On Fri, 2004-08-20 at 21:41, Wieslaw Faruga wrote:
> Hi,
> 
> W liście z pią, 20-08-2004, godz. 12:48, Thomas Dingler pisze: 
> > Hi,
> > 
> > I have a small (ok, big) problem.
> > 
> > When I create a object in the database, or change a object that ends
> in 
> > a transaction, all loaded database objects are are stored. This means 
> > all objects are serialized on every transaction, which needs much
> time.
> 
> Database objects (ozone objects) with a same permissons are grouped into
> clusters. Each cluster is serialized and written to a file as whole. The
> cluster size is limited to 64K. Thus if you create a small amount of
> ozone objects these objects will be written together. 

One can (apart from changing the cluster size with a parameter) also
'move' more code into ozone objects so that creating n objects is
condensed into a single transaction.

Cheers,
Leo

-- 
Leo Mekenkamp; phone: +31 641234919
Care about freedom and innovation? http://openoffice.org,
http://ozone-db.org, http://mozilla.org, http://linux.org



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285