There is a switch that lets you do local call optimisation (noLocalCopies=true). But there is still al lot of overhead affecting raw performance.
/johan -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Bresnahan Sent: den 9 april 2002 02:14 To: [EMAIL PROTECTED] Subject: Re: SSB vs. Singleton > Your points are well taken. However, I am not so worried about raw > performance. For example, most containers seem to optimize the SSB > method call and pass-by-reference in a same-JVM scenario (part of my > stipulation). WebSphere 4.0 does not appear to optimize local calls. The 10000:1 data I quoted was collected from a WebSphere 4.0/Win2K installation. > Am I missing something? I don't think you're missing anything. Stateless session beans will always be a loser if your only criteria is performance. Mike Bresnahan =========================================================================== 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".
