Smalltalk › Pharo › Pharo Smalltalk Users

Fuel and graph update

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

HilaireFernandes

Fuel and graph update

Hi,

I want to use Fuel to persist a graph in file.

The classic use case is "modify some part of the model and persist
immediately".

Now, it is not really efficient to re-serialize the whole graph each
time, and I am wondering how you are approaching this particular point
when using Fuel as your persistence back-end.

For example, various ideas coming to my mind:
- Is it possible to update some part of an already serialized graph?
- Should the graph be cut to pieces and serialized in several files?
- Or is Fuel fast enough to just re-serialize the whole graph?

How about you?

Thanks

Hilaire

--
Dr. Geo
http://drgeo.eu
http://google.com/+DrgeoEu

http://drgeo.eu

Mariano Martinez Peck

Re: Fuel and graph update

On Tue, Jun 9, 2015 at 9:21 AM, Hilaire <[hidden email]> wrote:

Hi,

I want to use Fuel to persist a graph in file.

The classic use case is "modify some part of the model and persist
immediately".

Now, it is not really efficient to re-serialize the whole graph each
time, and I am wondering how you are approaching this particular point
when using Fuel as your persistence back-end.

For example, various ideas coming to my mind:
- Is it possible to update some part of an already serialized graph?
- Should the graph be cut to pieces and serialized in several files?
- Or is Fuel fast enough to just re-serialize the whole graph?

For Quuve app, when it runs on Pharo (for development and testing), we have a fuel backend and we do 2) and 3) of above. Quuve itself is split in different/isolated conceptual databases: clients, advisory, securities, system, application, etc. So each of them is a database. And yes, we have a fuel file per database and for each save we serialize the whole graph. You need to be careful about cross-references between databases....

Anyway, it works good enough for our scenario. Our database are around 5MB and the serialization is immediate.

How about you?

Thanks

Hilaire

--
Dr. Geo
http://drgeo.eu
http://google.com/+DrgeoEu

Mariano
http://marianopeck.wordpress.com

HilaireFernandes

Re: Fuel and graph update

Le 09/06/2015 14:48, Mariano Martinez Peck a écrit :

> For Quuve app, when it runs on Pharo (for development and testing), we
> have a fuel backend and we do 2) and 3) of above. Quuve itself is
> split in different/isolated conceptual databases: clients, advisory,
> securities, system, application, etc. So each of them is a database.
> And yes, we have a fuel file per database and for each save we
> serialize the whole graph. You need to be careful about
> cross-references between databases....
> Anyway, it works good enough for our scenario. Our database are around
> 5MB and the serialization is immediate.
>

The perspective looks great. I don't need concurrent write access, and I
am anticipating the graph remains far bellow 5MB, likely bellow 100 KB.
I am just testing it and one fuel file per graph looks great, and it is
so comfortable!

Thanks

Hilaire

--
Dr. Geo
http://drgeo.eu
http://google.com/+DrgeoEu

http://drgeo.eu