Thanks Peter for your quick answer. But I think I found the reason meanwhile and it was extensive use of nested divs. Thus it was a client side issue and had nothing to do with A4D.
I've reworked the layout and replaced a lot of divs with spans and margin-right css and time now is down to 700 ms latency and 1.8s loading time for a batch size of 100, which is acceptable. Anyway I find it misleading, that Safari seems to calculate rendering time into the reported loading time. Well, seems I have to spend a bit more time learning the Safari console. ;-) Peter > Von: Peter Jakobsson <[email protected]> > Antworten an: Active4D Developer Discussion List > <[email protected]> > Datum: Fri, 23 Nov 2012 18:31:01 +0100 > An: Active4D Developer Discussion List <[email protected]> > Betreff: Re: [Active4d-dev] Tracking performance bottlenecks > > > On 23 Nov 2012, at 17:01, Peter Gutbrod wrote: > >> I'm wondering what is going on to take 14s for sending the page. > > Auxiliary requests ? > > Are you sure the 14s relates to the original request only and not for the > overall page content ? (i.e. stylesheets, images, scripts and whotnot). > > Peter > > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://list.aparajitaworld.com/listinfo/active4d-dev > Archives: http://active4d-nabble.aparajitaworld.com/ _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
