> From: "Hendrik Schreiber" <[EMAIL PROTECTED]> > Reply-To: "Research Triangle Java User's Group mailing > list."<[EMAIL PROTECTED]> > Date: Wed, 19 May 2004 14:49:27 -0400 > To: "Research Triangle Java User's Group mailing list." <[EMAIL PROTECTED]> > Subject: Re: [Juglist] Remote deployment to WebsphereApplicationServer? > >> What is your container config? Can you post your descriptor (ejb-jar.xml, >> jboss.xml and jbosscmp-jdbc.xml)? I want to see what fields you're eager >> loading as well as what you're caching, marking read only (to prevent >> transaction locking) and what locking policies you're using (if collisions >> are rare then do you need pessimistic locking?) > > We are using BMP. So I guess, there isn't a lot with respect to locking that > can be tuned. >
NEVER use BMP if you care about performance. BMP is as Gavin said the other night, broken. If you HAVE to write your own DB code, go all the way with Session beans that make value objects. Don't bother with BMP, it only buys you Container Managed Transactions. Do you have "Requires", "RequiresNew" or so forth? If everything is going to the database anyhow why bother with appserver locking at all? CMP will let you have caching and is the best hope for high performance. It will also prevent the n+1 load problem if tuned right: (finder = 1 query, every bean's ejb-load is another query) -Andy _______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
