Current time: 10-22-2019, 03:48 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Limits on number of tests
11-11-2016, 07:59 AM
Post: #1
Limits on number of tests
I can't find documentation on the subject. I have one private server with 4 clients and run many automated tests throughout the day. I'm starting to see large queues in the jobs directory. Is anyone aware of the practical limits per single private wpt server?
Find all posts by this user
Quote this message in a reply
11-12-2016, 08:23 AM
Post: #2
RE: Limits on number of tests
Oddly enough I found what I thought to be the root test in the queue but it claimed to be waiting for 1 test to be done. looking at the timestamps and names of the jobs in the works/jobs dirs, i found only one test that could be the cause so i check the status on that guy. It stated it was behind 269 others. I'm confused as to whats happening here
Find all posts by this user
Quote this message in a reply
11-12-2016, 09:00 AM
Post: #3
RE: Limits on number of tests
Sounds like there are more tests being submitted than you have test agents to handle. A single server can have hundreds of test agents with no problem (and multiple can poll the same location for work). Sounds like you need more test agents to satisfy the testing. Each agent can only run one test at a time and the number of tests a given agent can go through will depend on how long each test takes (connection settings, website speed, etc).

As far as queue position goes, it will depend on the priority of the test (.p# extension). Lower priority (higher number) tests are queued behind higher priority tests so if someone is running tests at top priority through the UI it could easily starve lower priority tests.
Visit this user's website Find all posts by this user
Quote this message in a reply
11-17-2016, 02:42 AM
Post: #4
RE: Limits on number of tests
(11-12-2016 09:00 AM)pmeenan Wrote:  Sounds like there are more tests being submitted than you have test agents to handle. A single server can have hundreds of test agents with no problem (and multiple can poll the same location for work). Sounds like you need more test agents to satisfy the testing. Each agent can only run one test at a time and the number of tests a given agent can go through will depend on how long each test takes (connection settings, website speed, etc).

As far as queue position goes, it will depend on the priority of the test (.p# extension). Lower priority (higher number) tests are queued behind higher priority tests so if someone is running tests at top priority through the UI it could easily starve lower priority tests.

Thanks Patrick. It looks like my private instance clients had run out of disk space. Chrome had been recording a crash dump on every run.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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