Re: Performance - JBoss/Hibernate caching versus versioning

Simon Brooke wrote:
> in message <1159758005.247001.29240_at_c28g2000cwb.googlegroups.com>,
> timasmith_at_hotmail.com ('timasmith_at_hotmail.com') wrote:
>
> > Hi,
> >
> > For scalability which do you think performs better? Assume Oracle 10g,
> > JBoss AS (x10), 1000 concurrent users (heavy transaction processing -
> > mostly reads).
> >
> > a) Let Hibernate/JBoss Tree Cache perform caching of active content -
> > AS pinging each other, keeping data in sync.
> >
> > b) Mark your objects with a version number and every time the object is
> > requested select the version number and if the object has not changed
> > return from cache.
>
> c) don't cache in Java at all, since caching is what Oracle is very good
> at. Don't use heavyweight data objects which are expensive to create on
> fetch from database. Play to the strengths of the technologies you're
> using, not the weaknesses. Really fetch from the database on each
> transaction.
>
> Read 'Better, Faster, Lighter Java'
> http://www.oreilly.com/catalog/bfljava/
>
> --
> simon@jasmine.org.uk (Simon Brooke) http://www.jasmine.org.uk/~simon/
>
> ;; making jokes about dyslexia isn't big, it isn't clever and
> ;; it isn't furry.

How do you scale out instead of up? I suppose you could spread your Oracle instances over multiple nodes? I would imagine licensing is fairly costly versus only paying for hardware for java application servers. Received on Mon Oct 02 2006 - 11:31:52 CDT