• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Troy W. · Oct 10, 2012 at 04:03 AM ·

Is EJB3 really as inefficient as dynaTrace indicated?

Hello Compuware staff,

We are running a standard EJB3 application. Our web server is a Linux machine running Tomcat. While our App server is a Linux machine running JBoss. Recently we closely studied the timing statistics of App server Stateless Session Bean call given by dynaTrace Purepath. Our study seems to indicate that EJB3's Stateless Session Bean calls are very inefficient. Only a tiny segment of the time is spent on the actual work. Most of the time is wasted in RMI overhead.

From the attachment one can see that the App server Stateless Session Bean call took 57.65 ms. This 57.65 ms approximately equals the sum of "defineClass0" (8.68) + "getCallerClassLoader()" (8.68) + "getMACSOptions()" (18.11) + "socketRead0()" (10.54) + "copyOf()" (11.64). Among them, only "getMACSOptions()" (18.11 ms) does useful work. The rest are all overhead. So the efficiency of EJB3 Stateless Session Bean call is only 31% !!!

I am wondering whether my observation is correct. I am also wondering whether you have similar past experience.

Thanks in advance.

Troy

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

2 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Troy W. · Oct 11, 2012 at 01:33 AM

Andi,

Thanks for your information. I have checked other Purepathes. I can see similar behavior there. The overhead time for each Stateless Session Bean call is always around 30ms.

Troy

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Andreas G. ♦ · Oct 12, 2012 at 04:51 AM 0
Share

in the PurePath dashlet click on "show all nodes". It will show you additional trace levels from Auto Sensors. The "copyOf" method call for instance might be from some other component.
My point is - you may want to see whether there is anything else going on in that request that is not Bean-related that causes this overhead. But - it might very well be that it has a certain amount of overhead

avatar image

Answer by Andreas G. · Oct 10, 2012 at 10:23 PM

Hi Troy

I am not sure if looking at a single purepath should lead to this conclusion. It seems that classes are created on the fly here. This "overhead" might just be a one-time thing. After starting your app your app still needs to fully initialize. Therefore I suggest to look into several PurePaths and see whether this pattern stays the same or changes over time.
Andi

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

2 People are following this question.

avatar image avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A