On 12/23/10 1:13 AM, manu.francis.mat...@accenture.com wrote:
Thank you very much for explaining so clearly.
One suggestion I don't think anyone here offered is running your
application in a profiler to see where it's spending its time. I've
found the one in NetBeans to be pretty good, and
Thanks Kushan
--- In str...@yahoogroups.com, Kushan Jayathilake kusha...@... wrote:
Addition to this, you can track response time with Firebug (Third party
plugin for Firefox) once it installed, open it's Net tab, and click or do
whatever action in your JSP page, after the browser received
,
9742260423.
Team Lead - Accenture.
www.accenture.com
From: Dave Newton [davelnew...@gmail.com]
Sent: Wednesday, December 22, 2010 10:33 AM
To: Struts Users Mailing List
Subject: Re: web application response time is too large.
On Tue, Dec 21, 2010 at 11:56 PM
Hi All
I have developed one web application in struts 1,
database as MS SQL server and it is deployed on tomcat 6 server (Window OS).
For certain pages response time is too large.
Test case:
(content on web page is too large like text box, buttons, images.)
Total Number of records: 284
The problem could be *anywhere*.
How are you going to start tracking it down? You must have *some* ideas of
where/how to look?
Dave
On Tue, Dec 21, 2010 at 12:19 PM, onlysameer_no1else sameer.pa...@gmail.com
wrote:
Hi All
I have developed one web application in struts 1,
database as MS
...@jakarta.apache.org
Subject: web application response time is too large.
Hi All
I have developed one web application in struts 1,
database as MS SQL server and it is deployed on tomcat 6 server (Window OS).
For certain pages response time is too large.
Test case:
(content on web page is too large like
...@jakarta.apache.org
Subject: RE: web application response time is too large.
What sort of validation mechanism and actions you are putting on your web form?
Anyway, you can try Jmeter to performance test your application.
Regards
Amit Oberoi
Sent from my Nokia E72.
-Original Message-
From
Hi,
You can do something like this, take the queries that in pages takes longer
time to load, then write a simple java programs to execute those queries,
1. print the time before it executes the query
2. print the time after it executed.
3. compare the values you get,
4. if its higher then your
On Tue, Dec 21, 2010 at 11:56 PM, wrote:
Are you sure that database is normalised as well..
Normalization can often *increase* response time, particularly for some
types of operations, because of the join overhead. The DB needs to be
correct for what it's being used for, and sometimes
Good points. However, I'd caution people to be careful of denormalization
-- if you don't normalize in the first place, you run the risk of degrading
performance in *other* ways ... not to mention opening the door for some
ugly data-consistency issues.
Like all things, there's a balance
Addition to this, you can track response time with Firebug (Third party
plugin for Firefox) once it installed, open it's Net tab, and click or do
whatever action in your JSP page, after the browser received it's response
you can see how long it has taken to load the content,
even It will show
I love Firebug. It's quite possibly the single best tool in my web
development toolbox.
-Brian
On Tue, Dec 21, 2010 at 11:15 PM, Kushan Jayathilake kusha...@gmail.comwrote:
Addition to this, you can track response time with Firebug (Third party
plugin for Firefox) once it installed, open
Yep. me too.. especially the facility to inspect and debugging Javascripts
:)
On Wed, Dec 22, 2010 at 10:57 AM, Brian Thompson elephant...@gmail.comwrote:
I love Firebug. It's quite possibly the single best tool in my web
development toolbox.
-Brian
On Tue, Dec 21, 2010 at 11:15 PM,
13 matches
Mail list logo
