Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <user@jmeter.apache.org>
Received-SPF: pass (nike.apache.org: domain of asp.adieu@gmail.com designates
 209.85.160.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAuw+CkH98aE3kyz76Mr9NZV5rYnKpyx6Lc=vtR9khe7aCoLZg@mail.gmail.com>
References: 
 <CAAuw+CkH98aE3kyz76Mr9NZV5rYnKpyx6Lc=vtR9khe7aCoLZg@mail.gmail.com>
Date: Fri, 7 Jun 2013 16:46:33 +0300
Message-ID: 
 <CANEEAczm=0aL-W1_UcBvb521Q=v+0JRfb=UyB22s-Rkjqs99Bw@mail.gmail.com>
Subject: Re: Measuring page load / rendering time
From: Adrian Speteanu <asp.adieu@gmail.com>
To: JMeter Users List <user@jmeter.apache.org>
Content-Type: multipart/alternative; boundary=bcaec52156d1b6460a04de90a843

--bcaec52156d1b6460a04de90a843
Content-Type: text/plain; charset=UTF-8

Hi,

I have a different approach to this. But there's a lot of background to it,
which can't be covered answering a specific question (how to measure X),
all of it resumes to: you should not look for shortcuts and instead should
do things the right way. Measuring rendering times is the complete opposite
of doing things that way. Its a dead-end, because it is too hard to track
and fully cover. Are you going to test on a large enough number of
PC/Mac/Linux hardware configurations in conjunction with a large number of
software versions (OS, browsers, other plugins that might affect
rendering)? Is your test matrix going to be comprehensive enough? Usually
its not.

The approach to front-end should be different because UI has different
specific problems. I use YSlow!, a plugin for Firebug that works on
Firefox. It shows "missing optimisations", and gives a good starting point
for a development team to obtain the best rendering time for their project.
With JMeter, you create the load on the server side and with one desktop
machine, you evaluate what will be the most probable user experience during
high traffic and then improve that. Its the best thing you can do, and the
only honest approach to this problem. You can still make measurement taking
several samples from tools like Firebug, Chrome's dev tools and so on, but
what's the point? Are you trying to benchmark the renderer or your server
application? If its the second, there are more questions you ask.

Regards,
Adrian S


On Thu, Jun 6, 2013 at 3:28 PM, nmq <nmq0607@gmail.com> wrote:

> Hi everyone
>
> I have been told that JMeter does not measure page load or rendering time.
> Does anyone know of a roundabout way of making approximations using JMeter,
> which would be fairly close to actual times.
>
> Or if anyone knows of a better tool that can be used to achieve this?
>
> The AUT is a secured web portal giving access to a limited number of users
> and is document intensive. I need to measure the page load time of the
> Documents page which displays the first 100 documents and as the user
> scrolls down, renders the next 100 and so forth.
>
> Any tips or help for load/performance testing would be appreciated.
>
> Thanks
> Sam
>

--bcaec52156d1b6460a04de90a843--