Re: [smila-dev] Binary Storage Service - voting request forhierarchical

[Ivan Churkin <ivan@xxxxxxxxxxxx>]

Hi,

> Disadvantages
> - mapping between hashed ID and persistence path needs to be stored
> - possibility of assync. situations between the existing storage persistence and stored mapping
>   

Maybe this simple solution will help to avoid that problems:

if HASH is "ABCD" then binary data stored to path "/A/B/C/D/data"

--
Ivan


Juergen.Schumacher@xxxxxxxxxxx wrote:
> Hi, 
>
> I'm not quite sure yet about what would be better, but ...
>
>   
> > - memory consumption and faster risk of OutOfMemory occurrence (the file system APIs creates listeners for all 
> > these sub-folders in order to provide cache (refresh) functionality, so for single record there will be 5 
> > listeners (4 sub-folders + 1 record) created and memory consumption increases significantly).
> >     
>
> ... is not really an argument for either solution. Half a memory leak is still a memory leak, and if this cannot be fixed in VFS, VFS is simply not appropriate for SMILA.
>
> Apart from this: I don't like this part of the first proposal:
>
>   
> > Disadvantages
> > - mapping between hashed ID and persistence path needs to be stored
> > - possibility of assync. situations between the existing storage persistence and stored mapping
> >     
>
> That sounds to complicated and error-prone.
>
> So, I think this means I'm for the second solution (implemented without memory problems).
>
> Cheers,
> Juergen.
> _______________________________________________
> smila-dev mailing list
> smila-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/smila-dev
>