[Seaside] Re: [Q] Question on Magma (or other Persistence Engine for Squeak/Seaside)

[Hilaire Fernandes]

Sungjin,

The slowness you are witnessing has not much to do with Magma. I think 
it is more of a design problem with the example. Starting a Magma 
session takes a couple of second as Magma check the integrity of the 
ODB. However one Magma session can last longer than a Seaside session.
Try to look at the archive of the Magma ml, some people are using pool 
of already started Magma session with Seaside to solve this problem.
Personnaly I have not yet addressed this problem. When using with 
Seaside I just use one single Magma session for all the Seaside session, 
but I will probably use the pool of Magma sessions when needed, if 
nothing better.

Hilaire


Sungjin Chun a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Brent Pinkney wrote:
> 
>>> Yes, I have almost no experience on this as you might already know, but
>>> I cannot find proper example for me. I'll look on sushi store example.
>> I wrote the sushi store example, so you can ask me directly.
>>
> 
> Hi,
> 
> Magma Version of Sushi Store Example (I've downloaded change set from
> wiki, seasideSushiStoreWithMagma.3.cs) is rather slow. It takes almost 3
> to 4 seconds to display each browse page. It seems that one magma
> connection is used for one session(right?), why is this slow? For me,
> it's slower than SQLite(FFI version), though I'm not tested directly.
> Are there anything I missed here? If this problem is known, what other
> ODB for squeak is recommended, OmniBase? SmartFileDictionary?
> 
> Thanks in advance.
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFGJdqSQqspS1+XJHgRAuTnAJ9+7DauBXlTTJiO0FSsSz6PGUnolgCgkTQh
> JY4QnAD6rVOyGGZtm9oVlDo=
> =WCIj
> -----END PGP SIGNATURE-----