You can blog, but bear in mind that the numbers might change. To be precise, the changes
that went into Beta1 are:
- Change from ByteArrayKey (wrapper) to byte[] keys
- Change from CacheValue (wrapper) to byte[] value
- Version stored directly in Versioned*Entry classes
So, this means that we loose two wrapper objects.
However, in next release, there will be a wrapper class in the value side (Metadata), but
stored internally, in a Metadata*Entry class (all Versioned* classes are heading out...).
So, we will gain one wrapper class. But it's worth calculating the memory consumption
then, and maybe think if we can optimise this away for Hot Rod.
REST and Memcached will do need to store the entire Metadata object. REST adds content
type and Memcached adds both version and flags.
Anyway, this is something we can tweak further, but I'm very pleased we have a
baseline for beta1, because we can see what the effects of supporting the other endpoint
compatibility.
Cheers,
On May 7, 2013, at 4:55 PM, Manik Surtani <msurtani(a)redhat.com> wrote:
On 7 May 2013, at 15:39, Martin Gencur <mgencur(a)redhat.com> wrote:
> I can make a blog post once we have this for Memcached and REST. I guess it is not
ready yet.
Yes please. Nice work. :)
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org