RE: [jbosscache-dev] Perf tuning for JBoss Cache

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. 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? 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: 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.