Scheduler (interval) is not working
This is happening in LoadUI Pro 2.6.x 64 bit (Windows 7) But there is no such problem in 2.1.2 The interval scheduler is not functioning correctly and even doesn't show the graphical part of the ...
Forum Discussion
SmartBear_Suppo
Alumni
AlumniHi payam,
I have downloaded the latest Open-source version of LoadUI (2.6.2), ran the exact same test as you but it worked as expected for me.
I actually just changed one thing: the Scheduler is supposed to go before the Generator, so you should have the following setup:
- Scheduler -> Generator -> Runner
In your description, you say you expect nothing to happen in the first 5 seconds. However, in the video, I can see you set "Start At" to 0.
Therefore, LoadUI should actually generate requests from the beginning of the test (t= 0s) until 5 secs later (t = 5s), because you set "Duration" to 5 secs. And in total, it should have generated 25 requests approximately, as you mentioned.
There seems to be something going wrong with your requests though. Notice that you got 10 rows in the Table Log already from the first moments of the test... also notice that your requests are failing, which is probably causing the unexpected results.
I suggest you try to find out why your requests are all failing (you probably should use your own server to check your load test setup, Google is very pro-active in blocking people who hit their servers more than they wish) then see if at least when your requests succeed, you get the expected results.... then we can check why when you have failed requests, LoadUI does not seem to generate the expected load (it could be due to numerous factors, such as the "burst size" you have set to you Generator - this is actually how many Virtual Users you want the Generator to represent -, maximum number of internal Threads used and internal thread queue size, which you can configure in the Global Settings, or your LoadUI environment being corrupt. In the latter case, you might want to do the following:
- In your ~/.loadui folder, delete the controller-cache folder. It's ok do do that, it just caches some LoadUI code to speed up startup...
- Restart LoadUI.
Regarding the fact that it "doesn't show the graphical part of the scheduler", you're absolutely right and we're very sorry for this problem! We will make sure to fix it as soon as possible.
Please let us know if we can do anything else to help you.
Best regards,
Renato
SmartBear Software
I have downloaded the latest Open-source version of LoadUI (2.6.2), ran the exact same test as you but it worked as expected for me.
I actually just changed one thing: the Scheduler is supposed to go before the Generator, so you should have the following setup:
- Scheduler -> Generator -> Runner
In your description, you say you expect nothing to happen in the first 5 seconds. However, in the video, I can see you set "Start At" to 0.
Therefore, LoadUI should actually generate requests from the beginning of the test (t= 0s) until 5 secs later (t = 5s), because you set "Duration" to 5 secs. And in total, it should have generated 25 requests approximately, as you mentioned.
There seems to be something going wrong with your requests though. Notice that you got 10 rows in the Table Log already from the first moments of the test... also notice that your requests are failing, which is probably causing the unexpected results.
I suggest you try to find out why your requests are all failing (you probably should use your own server to check your load test setup, Google is very pro-active in blocking people who hit their servers more than they wish) then see if at least when your requests succeed, you get the expected results.... then we can check why when you have failed requests, LoadUI does not seem to generate the expected load (it could be due to numerous factors, such as the "burst size" you have set to you Generator - this is actually how many Virtual Users you want the Generator to represent -, maximum number of internal Threads used and internal thread queue size, which you can configure in the Global Settings, or your LoadUI environment being corrupt. In the latter case, you might want to do the following:
- In your ~/.loadui folder, delete the controller-cache folder. It's ok do do that, it just caches some LoadUI code to speed up startup...
- Restart LoadUI.
Regarding the fact that it "doesn't show the graphical part of the scheduler", you're absolutely right and we're very sorry for this problem! We will make sure to fix it as soon as possible.
Please let us know if we can do anything else to help you.
Best regards,
Renato
SmartBear Software