Question

Neoload is taking 10 mins to start running a test after clicking on start scenario

  • 4 April 2024
  • 4 replies
  • 36 views
S
Badge

After clicking on run, NeoLoad is taking ~9-10 mins to start the actual test. It is same from NeoLoad web as well. How can I reduce this time to <5mins?

I need to reduce this time as I need to do some debug work with other team and its waiting for 10 mins to start the test which is just time consuming.

this is the different sizes of relevant folders in NeoLoad which are more than 1 MB:

Zip folder size using “Export Project to Neoload web” : ~19 MB

.git folder: 1.45 GB (might not be relevant here)

recorded request: 11Mb

Recorded response: 900 MB

Recorded screenshot: 21 MB

Results: 300Mb

Variables: ~60Mb

Some Config.zip.bak files :~50 mb

 

I am not sure which file/folder is contributing to the increase of this delay in starting the test. Can anyone please help me with it?

 

 

4 replies

N
Userlevel 1
Badge +1

Hello, your project size seems big but it should not take so much time to start. What can slow down the starting process is anti-virus that scans the files sent by NeoLoad to the LG’s, the network bandwidth available on controller to send data to the LG’s, slow disk access while zipping the project etc...

Do you also get that behavior with one LG or with multiple LG’s?

You should check with the task manager if there’s any processes using CPU (except NeoLoad) while starting the test. Also check the memory consumption of the NeoLoadGUI.exe process in case you run out of memory or near the limit.

Since your project is a collaboration one you could try to “Save as” it to unshare it. This will reduce a lot the number of files inside your project. This is to eventually avoid any issues with high number of files.

 

S
Badge

I tried to run it from 1 LG (directly from the system) and with 10 Lgs (with Neoload web) and in both the time it is taking ~10 mins.  I tried to do a save as today for this project and it took ~30 mins and then also it did not do the Save as. 

I am thinking of deleting some of the userpaths which I no longer use. But I am not sure whether that will help in this situations.

N
Userlevel 1
Badge +1

The fact that the “Save as” took around 30 mins and it did not succeed seems to confirm an environment issue. Like as i said before the number of files in a NeoLoad projects shared to a git repo may be huge. You should check if your disk is not too slow or if your project is not stored in a network shared which will be the root cause of your issue. Also again an anti-virus may also slow down that saving process.

S
Badge

I am able to fix the mentioned issue of ~10 mins to start.

I have removed all the unnecessary userpaths from my scripts. Also I have removed all the disables components inside the script which I dont use. Example- While recording the script I  record all the requests like css png etc which I just disable while running my actual test. I have deleted all of them and removed all extra things like extra servers, userpaths, scenarios, populations. what mainly reduced the starting time was removing extra userpaths and extra components (disabled components) like png css etc. 

 Currently its taking 3-4 mins to start as I have ~100+ userpaths (more than long 10+ UI flows with 10-50+ transactions.

 

Reply


ShiftSync Terms and Conditions

Copyright ©2024 Tricentis. All Rights Reserved.