Re: Atomicity with reiser4?

[Hans Reiser <reiser@namesys.com>]

Nicolas Smallwood wrote:

>Its an internally built B Tree database that uses 4k blocksizes.
>Inside, we were loading "u-forms", a concept we use that involves
>having a UUID, and an e-form composed off attribute names and their values.
>Most of these are no more than say 17k.
>
>To ensure that writes do occur, we open transactions for every access to the
>b tree,
>and closing a transaction will call fsync.
>
>My test involved 20,000 u-forms, which would of course call fsync 20,000
>times.
>
>Using another of the filesystems, each is under or around two minutes with
>fsync.
>
>Based upon what you where telling me, is the size of an atom configurable?
>Or what is considered too large?
>
>Thanks,
>
>Nicolas Smallwood
>
>
>
>
>  
>
You might consider creating u-form item plugins and doing it within 
reiser4.....  performance should be drastically improved by that.....