Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4771005
Votes 0
Synopsis PIORB is slow when ClientRequestInterceptor is used
Category idl:poa
Reported Against 1.4.1 , 7.0se , j2ee1.3.1-fcs
Release Fixed 1.4.1(1.4.1_02)
State 11-Closed, Unverified, bug
Priority: 2-High
Related Bugs 4744286 , 4773412
Submit Date 30-OCT-2002
Description
Problem Description:
-----------------------
We are seeing extremely poor performance from the PIORB when client 
interceptors are installed. I have a test which does a void-void ping on a 
remote server. On the ORB without any interceptors I can do about 100000 
invokes in 70s. If I install a null interceptor (every method does nothing) 
this drops to 100000 invokes in 200s. Stranger still the results get worse 
the longer I run the test for. So 10000 invokes complete in 10s and then 
increases non-linearly - 20000/21s, 30000/35s, 40000/50s ...

Attached is a testcase. You will need an appserver to deploy the RMI object 
on (or you may be able to do it with the JDK orb. It is dependent on your 
server being quick enough to sustain the load.

unjar and build. Deploy PingerImpl in your appserver.

To run you need to do:

java -classpath . piorbtest.PIORBTest <url> 100000

where url is the address of your CosNaming service that is hosting the RMI 
object.

The test runs for me in 246s. If I remove the call to 
add_client_request_interceptor it runs in 76s. Note that I am not doing 
set_slot or anything like that.

*****************************************************************************

 xxxxx@xxxxx  2002-12-10

Fix verified OK.

With build - j2sdk-1_4_2-beta-bin-b09-solaris-sparcv9-04_dec_2002
With test  - tests/performance/interceptors

*****************************************************************************
Work Around
N/A
Evaluation
We have measured the impact of PI in the past and did not see this magnitude of slowdown. 


 xxxxx@xxxxx  2002-11-19  Using a test produced by Sony I can reproduce the slowdown and see a memory leak.  I have found and fixed the problem.


 xxxxx@xxxxx  2002-12-20 This is a problem in both the Mantis code
base and in the SunOne Application Server code base.  This fix plugs a memory
leak which occurs in the ORB of the S1AS7.0 container and needs to be fixed
in an update release there as well.
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang