Can you quickly point out some entity bean optimizations/best practives, the more specific the better (besides standard ones like coarse grain, session wrapping entity beans, value objects, etc.) I think my problem was with the entity bean hitting to database way too often because the db share was true and my delay updates until end of transaction was false. It just seems to be that entity beans should be somehow cached better. -- Tinou Bao www.tinou.com ----- Original Message ----- From: "Cedric Beust" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 04, 2001 9:53 AM Subject: Re: [EJB-INT] entity bean performance (again...) / vendor implementation > > From: A mailing list for Enterprise JavaBeans development > > [mailto:[EMAIL PROTECTED]]On Behalf Of Tinou Bao > > > From reading the archive and other discussion lists entity bean > > performance has been a major point of debate. My experience has been that > > entity beans are a performance hit. > > Let's take the opposite approach: could you describe your overall > architecture and the performance problems you observed, maybe I can come up > with some useful hints (especially if you're running Weblogic ;-)). > > I have observed that a lot of our customers (and probably other vendors' as > well) use only a fraction of the optimizations that their server provides > for them. > > -- > Cedric > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
