On Dec 8, 2010, at 22:49 , Mariano Martinez Peck wrote: > On Wed, Dec 8, 2010 at 10:33 PM, Adrian Lienhard <[email protected]> wrote: > >> Hi Martin, >> >> I took some application for which we use image segments to test Fuel >> >> - With Fuel serializing and writing to disk took 330s. File size is 16.1MB >> - With image segments saving takes 4s and the file size is 2.4MB >> > > but how are you using ImageSegment? just the primitive? because in order > to compare it to Fuel, you should write all objects, including > "outPointers". So you should use #writeForExportOn: or similar...
yes, this includes outPointers serialized with reference stream and writing to disk. Adrian BTW, I was just providing the numbers that I gathered when looking at Fuel (to see whether that could be interesting for our use case to replace image segments). This was not to say that Fuel is not on the right way or anything, but I though the numbers would be interesting for Martin because they show a real-world use case with a large number of objects. I know that Fuel is in an early stage of development and it doesn't (yet?) have a primitive/plugin to speed things up.
