Hmm, except that when I'm testing here I'm seeing the same problems- I can access the same remote URL with both IE and FF and see these long lags in IE.
Testing locally, the response time is identical and very fast for both browsers. On Thu, Jan 31, 2008 at 1:08 PM, David Delbecq <[EMAIL PROTECTED]> wrote: > Random guess: > could it be your IE7 clients are configured to use a not so performant > proxy ? Using complex forms with IE7 here, no special troubles > En l'instant précis du 31/01/08 13:42, caped crusader s'exprimait en ces > termes: > > Thanks for the suggestions everyone. > > > > Our pages are very simple, very few images, very little javascript, and > > we're not using any extra javascript libraries. > > > > There is nothing obviously different in the server logs in terms of the > > files being fetched. I'm going to try the suggestions here and see if > what > > turns up. > > > > The puzzling aspect is the very large difference in time (by a factor of > 4) > > between IE and Firefox. This makes me wonder is there a difference in > how IE > > is handling either caching or if it is waiting for everything in the > page to > > load before rendering it to the screen, whereas FF is perhaps rendering > the > > page, but allowing non-visible elements to download in the background. > Mind > > you, in FF, the browser progress bar, which presumably the download > status > > of all elements on the page, completes in 6-7 seconds, compared to the > 23 or > > so of IE. > > > > JM > > On Thu, Jan 31, 2008 at 8:46 AM, David Delbecq <[EMAIL PROTECTED]> > wrote: > > > > > >> Using ctrl-I on firefox , in the medias tab you will get an idea what > is > >> loaded by pages. If you see tons of javascript, css and picture, that > >> might be the source of your problem. Note that we had a similar problem > >> here once, JSF was slow to render (same time for IE / firefox), we > >> discovered we had a filter in our config that was, for database > >> transaction reasons, limiting request to one request at a time per > >> session (use of synchronized block on user session). As a result, all > >> queries for JS/CSS/pictures coming from JSF component where queued and > >> serve one at a time instead of in parallel. > >> > >> Even complex JSF pages shouldn't take 23 seconds to be returned to > >> client. Also note that complex css layout can sometimes takes time to > >> get rendered client side, but 23 seconds.... ? Even 6 seconds is far > too > >> much for average users :) > >> > >> > >> En l'instant précis du 31/01/08 09:15, Christopher Cudennec s'exprimait > >> en ces termes: > >> > You should try a tool like ProxySniffer or a plugin for FF or IE to > >> > >>> see why your page performance is that bad. We had some problems in our > >>> project concerning included css and js-files. You should be able to > >>> see who's "responsible". > >>> > >>> Cheers, > >>> > >>> Christopher > >>> > >>> Martin Marinschek schrieb: > >>> > >>>> Are you using any javascript libraries? Dojo? > >>>> > >>>> > >>>> > >>>> regards, > >>>> > >>>> Martin > >>>> > >>>> On 1/30/08, Simon Kitching <[EMAIL PROTECTED]> wrote: > >>>> > >>>> > >>>>> ---- caped crusader <[EMAIL PROTECTED]> schrieb: > >>>>> > >>>>> > >>>>>> Hi > >>>>>> > >>>>>> I have a JSF application with some quite unusual performance > >>>>>> > >> problems. > >> > >>>>>> Loading pages in IE7 takes 4 times as long as in Firefox (v2.0.0.11 > ) > > > -- > http://www.devlog.be (a belgian developer's logs) > > >
