Response time for all the components of a page

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Response time for all the components of a page

viji1188
Hi,

I use nGrinder 3.1.1 and JDK version 1.7.0_10.
In most of the tools the response time for a page includes: response time for each component in the page and not just the complete document load time.

Does nGrinder provide ability to receive response time for all the components in the page along with the complete page/document load time?
OR
Is there any other way to get the response time for each component on a page?

Thanks
Vij
Reply | Threaded
Open this post in threaded view
|

RE: Response time for all the components of a page

junoyoon
Administrator

Hey. vjji. nGridner 3.1.1 works there? 

 

-----Original Message-----
From: "viji1188 [via ngrinder]"<[hidden email]>
To: "junoyoon"<[hidden email]>;
Cc:
Sent: 2013-01-30 (수) 16:01:23
Subject: Response time for all the components of a page

Hi,

I use nGrinder 3.1.1 and JDK version 1.7.0_10.
In most of the tools the response time for a page includes: response time for each component in the page and not just the complete document load time.

Does nGrinder provide ability to receive response time for all the components in the page along with the complete page/document load time?
OR
Is there any other way to get the response time for each component on a page?

Thanks
Vij


If you reply to this email, your message will be added to the discussion below:
http://ngrinder.642.n7.nabble.com/Response-time-for-all-the-components-of-a-page-tp197.html
To start a new topic under ngrinder-user-en, email [hidden email]
To unsubscribe from ngrinder-user-en, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

RE: Response time for all the components of a page

junoyoon
Administrator
In reply to this post by viji1188

Not like you think, the most of load test tools does not support this. 

It's because this feature involves the HTML parsing, and it need a lot of processing. And.. finally it's not possible to run this kind of task in the multiple threads.


The cloud test service named BrowserMob supports this. However I'm quite suspecting how many vuser they can generate. Because of the the browser executing loads, they might not support many vusers.

The one option you can do is.. to upload the webdriver and htmlunitdriver jar file..

and write the test with this. http://code.google.com/p/selenium/wiki/HtmlUnitDriver

However it might not be easy to determine the page load end. You may have to find out the way for this.

HtmlUnitDriver does not load images and media files.. so it might not be accurate either.

 

Another option you can do is to use phantomjs and ghostdriver (which is a webdriver port for phantomjs)

http://phantomjs.org/

https://github.com/detro/ghostdriver 

It might exactly supports what you want.. however you have to find out the way to summarize HAL the phantomjs supports.

 

The last option you can do is to record the website traffic with TCPProxy which grinder provides.

Just make all request recorded by TCPProxy and put the generated script in nGrinder.

 

 

-----Original Message-----
From: "viji1188 [via ngrinder]"<[hidden email]>
To: "junoyoon"<[hidden email]>;
Cc:
Sent: 2013-01-30 (수) 16:01:23
Subject: Response time for all the components of a page

Hi,

I use nGrinder 3.1.1 and JDK version 1.7.0_10.
In most of the tools the response time for a page includes: response time for each component in the page and not just the complete document load time.

Does nGrinder provide ability to receive response time for all the components in the page along with the complete page/document load time?
OR
Is there any other way to get the response time for each component on a page?

Thanks
Vij


If you reply to this email, your message will be added to the discussion below:
http://ngrinder.642.n7.nabble.com/Response-time-for-all-the-components-of-a-page-tp197.html
To start a new topic under ngrinder-user-en, email [hidden email]
To unsubscribe from ngrinder-user-en, click here.
NAML