Current time: 02-27-2021, 02:23 PM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Webpagetest limitations
10-06-2011, 02:27 AM
Post: #2
RE: Webpagetest limitations
(10-05-2011 09:51 PM)zane Wrote:  1. Concurrent tests. It seems that the model for webpagetest is based on a single queue of pages that need to be processed. Is there any way to process more than one page at a time with the current system? If not, is there a possible way around it (I am prepared to work on the feature myself). Is this a limitation in the packet capturing or the browser or something else?

Are you just looking for the ability to run more tests or do you need to schedule multiple to execute at EXACTLY the same time? Each work queue can have multiple agents pulling from the queue so you can run as many tests in parallel as you have agents (always could). The Dulles location for the public instance is running 16 IE8 agents for example. You just configure them all to pull from the same work queue.

(10-05-2011 09:51 PM)zane Wrote:  2. The user needs to be logged in to get screenshots. I *think* I had problems with the screenshots or video when I was not directly logged in to the server (my memory is a little fuzzy). I tried hosting this on a VPN with remote desktop access. Does webpage test work correctly if there is a logged in user session without the user actually viewing the remote desktop? What is the recommended way to set up the server?

Yes, the user needs to be logged in. The easiest way to do it is to just configure Windows to automatically log in the user at boot time. If you RDP to a VPS, just reboot the system when you disconnect and it should work fine (That's how the Delhi agent and the EC2 instances are running). Another option is to run VMWare ESXi on a physical box and run the test agents as VM's (this is how Dulles is configured).

(10-05-2011 09:51 PM)zane Wrote:  Also, I would like to use the scripting system to test a series of steps. I haven't actually looked into this much yet but I will soon. I am just mentioning this here in case any problems/limitations with the scripting system come to mind.

The main limitation is that you can only record performance data for one of the steps in the script (well, to be honest, you can record them all but the UI gets confused). Better reporting for multi-step scrips has been on my to-do list for a while.


Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
Webpagetest limitations - zane - 10-05-2011, 09:51 PM
RE: Webpagetest limitations - pmeenan - 10-06-2011 02:27 AM
RE: Webpagetest limitations - zane - 10-06-2011, 04:02 PM
RE: Webpagetest limitations - pmeenan - 10-06-2011, 11:10 PM
RE: Webpagetest limitations - zane - 10-07-2011, 11:11 PM

Forum Jump:

User(s) browsing this thread: 2 Guest(s)