Le 08/29/12 15:54, Leonardo Santagada a écrit :
> On Mon, Aug 27, 2012 at 9:37 AM, Vincent Pelletier 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:
On Mon, Aug 27, 2012 at 9:37 AM, Vincent Pelletier 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
__
On Tue, Aug 28, 2012 at 12:31 PM, Vincent Pelletier 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 d
On Tue, Aug 28, 2012 at 06:31:05PM +0200, Vincent Pelletier wrote:
> On Tue, 28 Aug 2012 16:31:20 +0200,
> Martijn Pieters wrote :
> > Anything else different? Did you make any performance comparisons
> > between RelStorage and NEO?
>
> I believe the main difference compared to all other ZODB Sto
On Tue, 28 Aug 2012 16:31:20 +0200,
Martijn Pieters wrote :
> Anything else different? Did you make any performance comparisons
> between RelStorage and NEO?
I believe the main difference compared to all other ZODB Storage
implementation is the finer-grained locking scheme: in all storage
impleme
2012/8/27 Vincent Pelletier
> Hi,
>
> We've just tagged the 1.0 NEO release.
>
> ...
Release highlights:
> - production-ready !
>
Is anyone using it in production with Plone 4? Is there performance
advantages over ZEO for Plone 4 users?
> ...
> What you need to know if you are used to ZODB fe
On Mon, Aug 27, 2012 at 2:37 PM, Vincent Pelletier wrote:
> NEO aims at being a replacement for use-cases where ZEO is used, but
> with better scalability (by allowing data of a single database to be
> distributed over several machines, and by removing database-level
> locking), with failure resil
On Mon, 27 Aug 2012 14:37:37 +0200,
Vincent Pelletier wrote :
> Under the hood, it relies on simple features of SQL databases
To make things maybe a bit clearer, from the feedback I get:
You can forget about SQL presence. NEO usage of SQL is as a relational
as a handful of python dicts is. Except
On Mon, Aug 27, 2012 at 2:37 PM, Vincent Pelletier wrote:
> Hi,
>
> We've just tagged the 1.0 NEO release.
>
> NEO aims at being a replacement for use-cases where ZEO is used, but
> with better scalability (by allowing data of a single database to be
> distributed over several machines, and by rem
