This content has been marked as final.
Show 5 replies
-
1. Re: Interceptor Performance
kabirkhan Feb 14, 2006 5:28 AM (in response to redijedi)Are you reading the annotation for every invocation? Bear in mind that the interceptor instances have the same lifecycle as the bean instance they are applied to, so this data can be cached.
-
2. Re: Interceptor Performance
bill.burke Feb 14, 2006 9:07 AM (in response to redijedi)
Is it just me, or is the performance of ejb3 interceptors very poor?
Is it me, or are you negative about everything?
We have done ZERO profiling. There's probably a bunch of things we can optimize. -
3. Re: Interceptor Performance
redijedi Feb 14, 2006 11:03 AM (in response to redijedi)Is it me, or are you negative about everything?
LOL. I just want to know if this is a known issue. It is a big one for us, as it pushed back a release that we are working on at my company. The application (ejb3 based) will not scale. Requests via 50 simultaneous users were taking in excess of 20 seconds - some as long as 45! We do have more profiling to do. I'll definately keep this forum updated, but the sql is very fast and the code is straight forward. I suspect it is something in ejb3 that is highly non-scalable. Right now, I'm hoping it's something as simple as the interceptors. -
4. Re: Interceptor Performance
slaboure Feb 14, 2006 11:22 AM (in response to redijedi)"bill.burke@jboss.com" wrote:
Is it just me, or is the performance of ejb3 interceptors very poor?
Is it me, or are you negative about everything?
We have done ZERO profiling. There's probably a bunch of things we can optimize.
LOL, what's up Bill, not in a good mood this morning? ;) -
5. Re: Interceptor Performance
bill.burke Feb 14, 2006 1:28 PM (in response to redijedi)If you can pinpoint the issues and post them as Jira tasks, I'll see what I can do for the next release. I find it odd that interceptors aren't scalable. Its probably something really really stupid.