My number one concern with performance is the ability for me to stop requests with a low-tech DOS. If I have one computer hit the refresh key on the browser, no other client can get a page until the refresh has completed. I am running Windows 2000 and Webware .5. I have seen a tremendous speed improvement when I moved from IIS 5.0 to Apache 1.3. However, I can still stop all request with a simple constant refresh. What it seems to me is that the request are not being served by threaded servers or that they are running synchronously. Maybe there are some setting I can use on Apache to send back the last request if the same request is made to the server simultaneously. I am too familiar with Apache though.
-----Original Message----- From: Chuck Esterbrook [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 04, 2001 1:38 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Webware-discuss] (no subject) At 11:06 AM 10/1/2001 -0700, Russell Blank wrote: >I am trying to optimize my webkit servlets and I was browsing the webware Why are you specifically trying to optimize them? What kind of performance issue are you having? BTW My number one optimization technique is to cache any information my servlets compute that can be cached. That means either computing in __init__, or storing computations in self.attributes which then get used the second time around. >admin pages. In the Servlet Cache by Path, I realized that I do not fully >understand the following settings: >created 1 (sometimes this is greater than 1) >instances Queue: [] lock <lock object at 00CDC738> >path C:\Inetpub\WebWare\WebKit\vcmr\select.psp >reuseable 0 (sometimes this is one) >threadsafe 0 (this is never one) >timestamp 1001553935 > >Can anyone give me a quick explanation on what these settings are and how >they affect the web servlets and performance? The "settings" are really in WebKit/Application.config. What you are seeing here is a _data structure_ that the app server holds internally. This structure keeps instances of your servlets around so that requests can be responded to more quickly. I think its interesting that this PSPs reusable is set to 0. I wonder if that could be source of slow down. Can you tell me, are your PSPs always 0 for reusable? What about .py's? Are the Queues always empty? >Additionally, does the performance increase with more threads for the App >Server? Does the amount of threads have anything to do with the number of >servlet paths (I have noticed that number at 11 when I only have 10 >threads). The number of threads are determined in AppServer.config. The min is 5 and it grows to 20. If you are actually getting more than 20 _concurrent_ requests at a time, then you may experience a boost by increasing this number. That will depend on multiple factors probably including Webware, your op sys and your servlets. The best way would be to try it and see. Are you already getting more than 20 concurrent users at a time? -Chuck _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
