Hello Stan,

I can not reproduce your figures. 

Currently it is important to set the "httpclient.authentication.preemptive"
parameter to true (both for performance and for bug fixing reasons).
There is an other performance area, which is not committed in http-client
yet. But this should not show this factor.

Do you have a special performance test program? Which HW are you running on?

Best regards,

Juergen

P.S. In my tests I did a put of a 2K file for 10000 times and the client CPU
consumption is about 2-3% only.


 -----Original Message-----
From:   [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
Sent:   Thursday, January 02, 2003 19.36 PM
To:     Slide Users Mailing List
Subject:        Slide 2.x client performance with new Commons-HttpClient


We pulled source code from slide on 12-19 and were able to build and deploy
everything on the client and server.  We immediately noticed a significant
performance degredation on roundtrip calls to the server from the Slide
client.  The degredation appears to occur on all method calls.

In testing, we replaced the Slide client API and Http Commons API with the
versions from 11-18 (before migration) and the performance returned to
normal.  In researching the changes, we changed the
"httpclient.authentication.preemptive" property to true so that credentials
would be sent on the first request.  We verified this change through
NetTool.  This still did not solve the performance problem.  The
degredation seems to vary from 10x to 30x slower for identicial requests
from the client.

Is it possible that something in the Slide client has not been updated to
correctly take advantage ofthe new HttpClient library??

Thanks in advance.

- Stan



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

If you received this e-mail in error please delete it and notify the sender
as soon as possible. The contents of this e-mail may be confidential and the
unauthorized use, copying, or dissemination of it and any attachments to it,
is prohibited.

Internet communications are not secure and Hyperion does not, therefore,
accept legal responsibility for the contents of this message nor for any
damage caused by viruses. The views expressed here do not necessarily
represent those of Hyperion.

For more information about Hyperion, please visit our Web site at
www.hyperion.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to