durusmail: durus-users: Re: A question about consistence in durus
A question about consistence in durus
2006-04-21
2006-04-21
2006-04-21
2006-04-21
Re: A question about consistence in durus
2006-04-22
2006-04-22
2006-04-22
2006-04-22
2006-04-22
2006-04-23
2006-04-23
2006-04-23
2006-04-23
2006-04-23
2006-04-23
Re: A question about consistence in durus
Jesus Cea
2006-04-23
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Binger wrote:
> How frequent are conflicts that could be avoided this way,
> and how costly are they?

As ever before, the problem is different environments :-). Durus is
clearly designed for mostly read applications. For example, a forum
server, or nearly static webserver. I'm using it out of design
parameters, for "a lot of writes" applications. For example, my mailbox
storage server (about 50% read and writes) or my GIS application (about
5-15% writes). In fact I have some applications were read are minimal,
and writes are very high. For example, statistics collection servers, a
linda blackboard server, checkpointing services, etc.

I'm fighting because I deeply feel that durus can be used efficiently in
that environment, without applications doing workarounds to avoid false
conflicts, durus server keeping a huge changeset per client connection,
or read clients waiting (unnecessarily) for other read clients. I feel
that those changes are simple enough, and useful enough for other users
to benefice of them.

I would like durus to be *THE* persistence server in Python world.

Seems that work wouldn't be useful for mems-exchange. That's fine. Just
let me to try :)

> If my memory is right, our applications often get attributes many tens
> of thousands of times for a single page.  Keeping attribute access
> time as low as possible makes every page faster, and the cost
> of conflicts, especially false ones, is kept lower.

Are you touching thousand of objects per page?. Or thousand of
attributes of "few" objects?. My proposal only penalize the first
attribute access to each object, not all accesses.

> I really like the Persistent and PersistentBase classes as they are.

Of course you are. Durus is your child. And a fine product, must I say.

Can it be improved?. I think so.

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea@argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea@jabber.org         _/_/    _/_/          _/_/_/_/_/
                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRErEr5lgi5GaxT1NAQJ7aAP/eHaf3Hw5nu/Pet12uoZO8SMOJ86dD1nP
+BKV3uA1kH8Cdb4spZaCI90KZLahA2tgVcaR35l31E1rKl95RGpNchTqxhzTG9VC
njODt6+iXIZaSeKCybJB/AtEOThVgyB4klmSBWVwfCvIWM9mwxmzvFz5AOy0ISmy
nFHwytfDiUE=
=p/2F
-----END PGP SIGNATURE-----
reply