From jim at zope.com  Wed Aug 29 13:21:09 2012
From: jim at zope.com (Jim Fulton)
Date: Wed, 29 Aug 2012 07:21:09 -0400
Subject: [Neo-dev] [ZODB-Dev] [announce] NEO 1.0 - scalable and
 redundant storage for ZODB
In-Reply-To: <20120828183105.20330a53@vincent-tkpad>
References: <20120827143737.2bc1a837@vincent-tkpad>
	<CAJkXj+af7PJCSYpfZVg7brH5ZCSyDLKGXoDOn+6=zB-bzq2UUQ@mail.gmail.com>
	<20120828183105.20330a53@vincent-tkpad>
Message-ID: <CAPDm-Fi9715pdXg0SqAkxymUjL66nKredOVvoLcUNfh-3D6rWQ@mail.gmail.com>

On Tue, Aug 28, 2012 at 12:31 PM, Vincent Pelletier <vincent at nexedi.com> wrote:
...
> I forgot in the original mail to mention that NEO does all conflict
> resolutions on client side rather than server side. The same happens in
> relStorage, but this is different from ZEO.

That's good.  I'd like to move ZEO in this direction.  I'd also
like to stop hanging conflict-resolution on classes and have
some kind of registry, so that people can set CR policies
independent of class implementation.

I didn't realize that relstorage did client side CR, but thinking
about it, it has to work that way, since there's no relstorage
server.

Jim

-- 
Jim Fulton
http://www.linkedin.com/in/jimfulton
Jerky is better than bacon! http://zo.pe/Kqm


From santagada at gmail.com  Wed Aug 29 15:54:27 2012
From: santagada at gmail.com (Leonardo Santagada)
Date: Wed, 29 Aug 2012 10:54:27 -0300
Subject: [Neo-dev] [ZODB-Dev] [announce] NEO 1.0 - scalable and
 redundant storage for ZODB
In-Reply-To: <20120827143737.2bc1a837@vincent-tkpad>
References: <20120827143737.2bc1a837@vincent-tkpad>
Message-ID: <CA+HFc8727qV5GtRU-Zj_z0t7KugwxQE1ay6unXCNXP0MbAh+9A@mail.gmail.com>

On Mon, Aug 27, 2012 at 9:37 AM, Vincent Pelletier <vincent at nexedi.com> wrote:
> We've just tagged the 1.0 NEO release.

any plans to support pypy in NEO? Once ZODB start to run on pypy it
would be cool to have relstorage/zeo or neo running on it as well.

-- 

Leonardo Santagada


From jm at nexedi.com  Wed Aug 29 18:37:22 2012
From: jm at nexedi.com (Julien Muchembled)
Date: Wed, 29 Aug 2012 18:37:22 +0200
Subject: [Neo-dev] [ZODB-Dev] [announce] NEO 1.0 - scalable and
 redundant storage for ZODB
In-Reply-To: <CA+HFc8727qV5GtRU-Zj_z0t7KugwxQE1ay6unXCNXP0MbAh+9A@mail.gmail.com>
References: <20120827143737.2bc1a837@vincent-tkpad>
	<CA+HFc8727qV5GtRU-Zj_z0t7KugwxQE1ay6unXCNXP0MbAh+9A@mail.gmail.com>
Message-ID: <503E4542.2090906@nexedi.com>

Le 08/29/12 15:54, Leonardo Santagada a ?crit :
> On Mon, Aug 27, 2012 at 9:37 AM, Vincent Pelletier <vincent at nexedi.com> wrote:
>> We've just tagged the 1.0 NEO release.
> 
> any plans to support pypy in NEO?

We're looking at pypy from time to time but there are at least 3 reasons preventing us to use it for NEO:

- sqlite3 is still significantly slower on pypy so it could not be used for SQLite backend.
  I've just tested the example on https://bugs.pypy.org/issue1070 with version 1.9.0 and it's more than 2 times slower and  what is suggested on https://bugs.pypy.org/msg3088 does not help.
- MySQLdb is C module. We'd have to use another library for MySQL backend but that should be quick to implement.
- For the client part, as you say, it depends on ZODB.

So it should be possible to use pypy with admin/master/storage nodes and maybe get better performance with MySQL backend.

> Once ZODB start to run on pypy it
> would be cool to have relstorage/zeo or neo running on it as well.
> 


Julien