tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bedrijven.nl" <maar...@bedrijven.nl>
Subject RE: Performance issue
Date Tue, 07 Sep 2004 08:16:17 GMT
Hi ADC,

First of all I use connection pooling (JSQLConnect) and put values in cache
(hashmaps) so constant data retrieved once and deliver many. Let give an
example of which pages this is happening:

search.jsp: this jsp has multiple dropdownboxes. The data will be retrieved
from the server in a Vector and this data is qua volume on both (the
development as production) server the same. That means that all the content
of the dropdownlists are the same. So I may expect that there is no
difference in volume?? Or do you ment something different with that?? On a
reload the data within the dropdownlists are retrieved from the servercache
(lookup data is stored in a HashMap). So I don't know that's the problem.
How do you solve this problem?? The problem now is that one applications
causes an error (i don't know what, since there is nothing within the log)
and tomcat restarts.

Maarten



-----Oorspronkelijk bericht-----
Van: Allistair Crossley [mailto:Allistair.Crossley@QAS.com]
Verzonden: Tuesday, September 07, 2004 9:01 AM
Aan: Tomcat Users List; maarten@bedrijven.nl
Onderwerp: RE: Performance issue


it's an interesting one and one that we found too between our dev 1 cpu,
w2k, 512mb ram, tomcat 5.0.19 and production 2 cpu, w2k, 1gb ram, tomcat
5.0.19. In both cases we use a content management system backend and sql
server. 

for us we found that the volume of content in our cms on the production box
was 10 times that of the development box and so this slowed the cms down
making it look like tomcat was taking its time. also the sql server load on
production is larger so database ops take longer.

you ought to consider whether any dependent backend systems like cms,
database, crm etc.. are used in a different way between dev and production.
i do not think your problem is tomcat.

cheers, ADC

> -----Original Message-----
> From: Bedrijven.nl [mailto:maarten@bedrijven.nl]
> Sent: 07 September 2004 08:30
> To: 'Tomcat Users List'
> Subject: Performance issue
> 
> 
> Hello all,
> 
> Maybe a rare question but it's very important for us. What's the case:
> 
> * I have a development environment running our applications 
> (simple server,
> WIN 2000 Server, Tomcat 4.0.24, struts, max memorysize appr. 320 MB)
> * I have a production environment running our applications 
> (extended server,
> WIN 2000 Server, Tomcat 4.0.24, struts, max memorysize appr. 1 GB, 4
> processors)
> 
> Now in our applications we have some jsp pages (i.e. 
> searchpages). So what's
> my problem. When I reload a page (submit some action the the 
> form/actionbean
> of struts) it's faster on our development system than on our 
> production
> system. So normally it's should be so that jsp files should 
> be faster on our
> production environment because the server is a lot "bigger". 
> On the other
> hand the compilation of jsp's is faster (as expected) on the 
> production
> environment. Are there some settings in server.xml (or 
> web.xml) that causes
> this???
> 
> Thx in advanced!
> 
> Maarten
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 
> 


<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> 
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href="http://www.qas.com">www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message