[Kst] [Bug 116461] getdata borks when the first field in the format file isn't (ASCII) alphabetically the first field.

George Staikos staikos at kde.org
Wed Nov 16 06:11:27 CET 2005

On Tuesday 15 November 2005 23:55, Barth Netterfield wrote:
> On November 15, 2005 07:10 pm, George Staikos wrote:
> > > This generally works pretty well in terms of assuring concurency across
> > > the dirfile.  This issue is, however, the biggest down side of
> > > dirfiles.
> >
> >   And anything else that writes non-atomically or non-transactionally.
> Heh.... Rock and hard place... the old boomerang format was flat fields. 
> When we tried to use them for BLAST we couldn't read a field fast enought
> to even keep up because you have to read everything to read anything.... 
> The BICEP experiment is using flat fields - with 100 detectors + aux fields
> - so to read 1 field is >100x slower for them than for a dirfile.  Of
> course they don't have problems with concurency :-)

  Wouldn't it be OK to still read only what is needed even if writes are 
atomic or transactional?  Then the only delay would be the time required to 
write one frame, at most.

> What we are using now seems to more or less work, though I am not
> completely happy with our current solution, as I'm not sure that there is
> any promise from the OS that it will work (is there?).

   I think it's safe enough.

George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/

More information about the Kst mailing list