-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Binger wrote:
> In Durus, as you know, all transactions are pushed through the
> single storage server to make sure they can be serialized.
> Do your applications really require global serialization?

I don't understand the point of this, related to the NEW_OID latency :-).

Some of my write intensive (or read intensive with poor hit ratio)
applications are already using multiple durus backends to improve
parallelism. For example, the mailbox server have about 15-20 durus
instances. Each incomming mail is stored in the "home" durus storage
server for that user.

And you already know that I would work in a more "parallel" durus
implementation :). For example, reads can be trivially parallelized.

> You could, however, keep track of the oids consumed during the
> serialization,
> and, in the case of a conflict, these oids could be restored to the clients
> pool of allocated oids.

That was my idea. When you do the abort, instead of simply clearing the
OIDs in the newly created objects, you can do the clearing as ever but
keeping a list with the "throwed" OIDs, that can be reused in another
future transaction, in probably unrelated objects.

> It seems like your applications are network file systems, except
> that the file system has no directories and only a very particular
> type of file.

You could see it that way. I call it an object store :P

In fact I have also "patched" durus to allow clients to be notified when
certain objects are modified. So I provide also a publish&subscribe
paradigm :-).

- --
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

iQCVAwUBRGtBrplgi5GaxT1NAQKy0QP+MeDDc6+VlQRYKHtSDACDJqSMajppzxqh
FHKLG3fd8o7jKDLv2QYLh4Ns2AJWs+aIEINEtDXozQvdYueIso+rdoVYw8pu2Hv9
8PoHSrmU6zfmOwkXBSiH9nzRekkjeSkmlVq5aB/c72Chgr1IVNSSYfJR6YUV9icV
qkBJr5SRHKk=
=YJDa
-----END PGP SIGNATURE-----