TWSD-1557:After VA creation the list retrieval time increases proportionally with the number of instances.
Review Request #1409 — Created March 2, 2026 and updated
| Information | |
|---|---|
| austin | |
| AVX2 | |
| rel_apx_2_7_5, rel_apx_2_7_6 | |
| TWSD-1557 | |
| Reviewers | |
| lucille, shuinvy, stevenku | |
Verified this issue on 2.7.5.7 on AVX7900 model
When I created 10 VA instances then between 1-10 VA creation took 24sec, but API response is average 900ms
When I created other VA instances then between 10-15 VA creation took 38sec, but API response is average 900-1000ms
VA list refresh or listing still needs to have a consistency because few taking 25sec and few 40 sec and all VA’s having same configuration.
Jira : https://arraynetworks.atlassian.net/jira/software/projects/TWSD/boards/62?jql=assignee%20%3D%20712020%3A64a4a8f2-81d8-4b7a-9664-f9019a720f96&selectedIssue=TWSD-1557
I ran a test on the 192.168.97.11 (AVX) with 13 VMs. The API execution time is now down to 5–6 seconds. Attached is a video for reference on jira ticket.
First, I focused on improving the data processing logic. I replaced the nested loops with Dictionary-based lookups for O(1) efficiency. I also replaced the RegexParser with a strip method to handle inconsistent double-newlines (\n\n) in the CLI output. These also resolves a critical silent bug in disk parsing that would cause system crashes as soon as external disks are utilized. and these changes brought the execution time down to approximately 7.5–8 seconds.
To further improve performance, I implemented Multithreading to parallelize the 10+ sequential CLI commands (including VA status and license checks). By running these queries concurrently, the total execution time was further reduced to 5–6 seconds for 13 VA instances.
Last one is fixed a NameError: renamed rst to res. The variable rst was defined but never used, while res was being accessed without initialization, causing an error.
