Skip to main content

Scalability

Announcements
QlikWorld 2023, a live, in-person thrill ride. Save $300 before February 6: REGISTER NOW!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QV Script Gen Tool - Troubleshooting

We are using the QlikViewTestScriptGeneratorGui.exe tool to test the performance of our server.  When we run the test we had it set to ramp up to 25 users in 2 minutes.  The test ran for 1 hour.  During that time we did not see the RAM increase at all on the server as more users were added.  The ram stayed at the same value as it was when the document was preloaded into memory.

When looking at the Assertions, Actions chart in the SC Results.qvw it appears that every action has an error.

How we find why each action is failing?

labelTotal countErrorsErrors %Errors dist
3,2163,216100.00%
Access Point  #1277277100.00%8.61%
Open Document  #3277277100.00%8.61%
Change Sheet  [SH10] #5277277100.00%8.61%
ListBox  [LB23] #7800800100.00%24.88%
ListBox  [LB30] #933100.00%0.09%
ListBox  [LB23] #1133100.00%0.09%
ListBox  [LB30] #1333100.00%0.09%
ListBox  [LB23] #1533100.00%0.09%
ListBox  [LB30] #1733100.00%0.09%
ListBox  [LB23] #10789789100.00%24.53%
ListBox  [LB23] #13781781100.00%24.28%

Thanks,

1 Solution

Accepted Solutions
Not applicable
Author

The problem was that the document was never being opened.  The document had a space in the name and was causing the open to fail.  This appears to be a bug since the documentation states that spaces are allowed.  We removed the space from the name and the test ran.

View solution in original post

3 Replies
Not applicable
Author

The problem was that the document was never being opened.  The document had a space in the name and was causing the open to fail.  This appears to be a bug since the documentation states that spaces are allowed.  We removed the space from the name and the test ran.

Sebastian_Fredenberg

Thanks for the feedback,

This will be addressed and fixed in the next version of the tool.

Regards

/Scalabilty Center

Daniel_Larsson
Employee
Employee

This issue has been addressed in the intermediate release 0.5.4531 now availablefor download.

Regards,

  Scalability Center