> -----Original Message-----
> From: Mariano Ortega [mailto:[email protected]]
> Sent: Friday, August 13, 2010 9:37 PM
> To: [email protected]
> Subject: Re: Slow response time only on the first request
> 
> I posted this issue 5 days ago and did not receive any comments so
> far...
> 
> Did anyone face this issue?
> 
> Any idea/suggestion about it?
> 
> regards,
> Mariano

I expect this is normal behavior.  The first run of any test case will
have to load classes, which is relatively expensive.  A real performance
measurement test will run the CUT first to make sure all the associated
classes are loaded.

> On Mon, Aug 9, 2010 at 10:47, Mariano Ortega <[email protected]>
wrote:
> 
> > Hi,
> >
> > I'm working on a project where we have decided to start given access
> to our
> > core functionality thru Web Services. After some research we choosen
> Apache
> > CXF.
> > During my analysis, everything works fine. I was deploying the test
> > services on a Jetty without Spring Support (CXFNonSpringServlet).
> >
> > Now, the problem arouse when I deployed the same code on a Weblogic
> server.
> > The issue is that the FIRST coming request takes lot of time (~7
> seconds)
> > and the subsequent ones take times <70 msec.
> >
> > I was some kinda confused about this behaviour, it would make sense
a
> small
> > increase in the first request 4 times at most but not some kinda
this
> > magnitude (100 times).
> >
> > I've changed the log level to FINEST and I'm seeing that this is
> happening
> > the First time the Interceptor Chain is called (invoke to
> handleMessage on
> > each input and output interceptors) -- see lines 892 to 1069 of the
> attached
> > zipped log file. When the next request is served -- see lines 1121
to
> 1274
> > -- this work pretty smooth.
> >
> > Just in case, reducing the log level does not make things better
> (first
> > request takes 6,5 seconds and next ones 30 msec)
> >
> > Do you have any ideas of what could be happening and how can I fix
> it?
> >
> > Thanks in advance,
> > Mariano Ortega
> >

Reply via email to