What kind of debugging/profiling have you attempted? I realize the
tooling in IE doesn't stack up too well vs. FF, but basic things like
alerts to narrow down where the delays are can still be done
effectively. You said it's an XSLT-based app for instance... are the
transformations being done client-side? Have you tried using something
like HTTPWatch (there's some free alternatives out there if you Google a
few seconds) which would tell you if it's transit time somehow, etc.
Those types of things can at least narrow the problem down a little.
Without knowing what your pages are doing, the description you gave of a
page with no widgets definitely doesn't sound right... that's why I'm
wondering where the XSLT is processed. Without knowing in more detail
how the app is architected, it's tough to make reasonable suggestions,
other than start with basic troubleshooting techniques, which is always
sound advice.
I can tell you we went through a ton of work in our app to get
performance up to par. This app is using Struts 1.x, but Dojo, and a
ton of AJAX and heavily client-side work... the single biggest
performance improvement we saw was moving all static content, including
Dojo, onto the web server. In fact, that alone made it acceptable,
anything beyond that improvement was cake.
Frank
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
(2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
(2007, Apress, ISBN 1-59059-816-4)
Java Web Parts - http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!
Dave Mills wrote:
I just recently tried extracting the contents of
org\apache\struts2\static into <context_root>\struts, though I also
tried to eliminate as much of the dojo/ajax content in my app as
possible. The whole app is pretty simple, mostly just displaying
read-only data to users.
The thing that I'm most confused/concerned about is the "broken"
functionality in IE vs FireFox. For example, "Account Summary" is
nothing more than getting a result set from a database, and displaying
it. There are literally no forms/widgets on the page at all. In FireFox
this page loads in a couple of seconds. In IE7, the screen disappears
and then sits there loading/spinning for literally 5 minutes before
either loading or getting a time out.
-----Original Message-----
From: Mike Jennings [mailto:[EMAIL PROTECTED]
Sent: Monday, December 10, 2007 3:04 PM
To: Struts Users Mailing List
Subject: Re: Poor Performance & Hangs in IE
If you are using the static functions like dojo, then extract it into
your public html directory so that they are not loaded from the jar.
Then turn off loading the resources static.
Dave Mills wrote:
I've got a Struts 2.0.11 app running on Sun Web Server 7.1, which I
recently re-wrote from an entirely Servlet/XSLT app. In pre-release
testing everything seemed to be working well in terms of performance
and
functionality.
However, when the app was moved into production (which is SSL) the
performance has been horrible. In FireFox things generally work, even
if
they're a little slow, but in IE many pages hang for 5+ minutes.
I removed all of the Dojo stuff, and that helped a little. I also
tried
going through the performance tuning stuff, but I'm unsure how to
track
down some of these issues.
I don't know if this is even likely to be Struts-related, but any help
would be great!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------
Spam/Virus scanning by CanIt Pro
For more information see
http://www.kgbinternet.com/SpamFilter.htm
To control your spam filter, log in at
http://filter.kgbinternet.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
