> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Robert S.
> Sfeir
> Sent: Wednesday, July 25, 2001 8:51 PM
> To: Orion-Interest
> Subject: Orion Performance Tuning
>
>
> Hello all,
>
> I've gone through and read most of the information posted from this list
> about improving the performance of Orion, and increasing the number of
> threads Orion uses to improve its overall performance under load.
>
> What I've been able to do so far, and it's helped a lot, is:
> 1- Added the -Xms and -Xmx switches to make sure Orion starts and
> uses more
> memory, they're set at 100MB and 300MB respectively, and Orion uses 175MB
> as soon as I start it up, and doesn't seem to grow past 177MB as the day
> goes one and it gets used.
>
> 2- I added the -server switch in front of the java command so we
> make sure
> we use the Server version of the HotSpot VM. (Boy does this thing pick up
> speed when using the -server switch!)
>
> Is there anything else that can be done, short of clustering, to further
> increase Orion's performance?
>
> My main objective is to make sure we don't get any more weird hangs and
> long wait times in Orion for no apparent reason. Perhaps increasing the
> number of threads Orion uses? I can't seem to find any definite
> answer on
> that.
>
> Our servlet seems to be fine, but sometimes when clicking through a test
> web site, one url request seemed to just sit there and hang, as if Orion
> was dead, but I could click and request a different URL and get immediate
> response. So I assumed it was threads in Orion which were not being
> managed properly.
>
> After making reading the posts to the list and making the the 2 changes
> above, the problem seemed to have gone away for the most part, except it
> still happens from time to time in Netscape, IE doesn't seem to have this
> problem. I can quit Netscape and go back in and the problem is
> gone for a
> while. There is no specific time frame for it to happen. It does happen
> consistently when I click, then stop for about 30-60 seconds, then click
> again or reload, and it just sits there and waits for the world
> to come to
> an end of something. Very bizarre.
Maybe you run the server and the browser on the same computer and usual
Netscape is very hungry on processor time, a problem encountered by me very
often
in a combination of IIS and Netscape;
Use Task Manager to see if this is the problem;
>
> Any ideas you may have would be of great help.
>
> Thanks
> R
>
>
> Robert S. Sfeir
> Director of Software Development
> PERCEPTICON corporation,
> in Joint Venture With JTransit
> San Francisco, CA 94123
> pw - http://www.percepticon.com/
> jw - http://jtransit.com
> e- [EMAIL PROTECTED]
>
