Re: [jbosscache-dev] Perf tuning for JBoss Cache
On 27 Nov 2006, at 17:06, Galder Zamarreno wrote:
Yeah, I was looking at using the VAM from TreeCache as well :-)
There's only one downside to using VAM in the JDBCCacheLoader. Any
data previously stored in the JDBCCacheLoader would not be
compatible from this version onwards, or I guess they'd have to
revert back to the old way.
I'm happy to break compat when moving to 2.0.0. This will happen in
so many other areas anyway.
Afaik, we can switch jboss serialization on/off, but not VAM (which
is used from JBossCache 2.0), can we? I guess we're moving up to
2.0 so this leap might be acceptable.
Ok, so if we have customers that want to switch to 2.0 but they
have loads of data already in the database, how could we ease the
transformation of any data that they might have in the database?
Write a 'bridge' app, which starts 2 instances of JBC (old and new -
can these even run in the same VM together?) and yanks data out of
one and into the other?
Any ideas?
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
IT executives: Red Hat still #1 for value http://www.redhat.com/
promo/vendor/
-----Original Message-----
From: Manik Surtani [mailto:manik@jboss.org]
Sent: 27 November 2006 17:55
To: Galder Zamarreno
Cc: jbosscache-dev(a)lists.jboss.org
Subject: Re: [jbosscache-dev] Perf tuning for JBoss Cache
On 27 Nov 2006, at 09:47, Galder Zamarreno wrote:
> I have updated it with a couple of JIRA.
>
> Are you guys happy with those? We had already talked about the
> connection pooling stuff. Check the other one regarding
> serialization in the JDBCCacheLoader.
Yes,, you have a +1 from me already. Regarding the marshallers,
could we use an instance of the VersionAwareMarshaller created in
TreeCache? Just pass this instance to the JDBCCacheLoader (and any
other cloaders that need to serialize objects, such as
TcpRemoteCacheLoader) and use the VAM's object{To|From}ByteBuffer()
methods. This way cloaders will be version-aware too, in the same
way replication code is, and we'll have some degree of interop.
(Sweet!)
I'm adding a getMarshaller() method to CacheSPI for this purpose to
cloaders have access to it.
>
> Galder Zamarreño
> Sr. Software Maintenance Engineer
> JBoss, a division of Red Hat
>
> IT executives: Red Hat still #1 for value http://www.redhat.com/
> promo/vendor/
>
> -----Original Message-----
> From: jbosscache-dev-bounces(a)lists.jboss.org [mailto:jbosscache-dev-
> bounces(a)lists.jboss.org] On Behalf Of Manik Surtani
> Sent: 21 November 2006 17:24
> To: jbosscache-dev(a)lists.jboss.org
> Subject: [jbosscache-dev] Perf tuning for JBoss Cache
>
> Guys,
>
> Every time we see or suspect potential inefficiencies in the JBoss
> Cache codebase (stuff we spot while working on other features or
> debugging stuff) we should note these down so they can be revisited
> later.
>
> At some point I do want to do a full performance analysis as well,
> but for the time being this could be useful to capture stuff we see
> as we go along.
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCachePerfAnalysis
>
> Cheers,
> --
> Manik Surtani
>
> Lead, JBoss Cache
> JBoss, a division of Red Hat
>
> Email: manik(a)jboss.org
> Telephone: +44 7786 702 706
> MSN: manik(a)surtani.org
> Yahoo/AIM/Skype: maniksurtani
>
>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev