question

mbarfiel avatar image
mbarfiel asked Spirent_Admin edited

Topology editor is not responding with large scale configuration

We have large scale test beds that have 100s of devices. We are adding "blocks" of devices to the topology with 30+ session profiles. It looks like the iTest topology editor barely responds to edits on the session profiles for each device. We bumped up the memory in the .ini file to 1024Mb but that only helped a little. The topology editor is almost useless at this point for editing objects. It does run OK after the changes are made.

 

It appears that the refresh operation starts after making a change to the session profiles (IP and name) and that refresh locks up the GUI. At the bottom, left corner of the screen you will see a refresh message displayed. The GUI remains unresponsive until that refresh operation completes.

 

Have we stumbled into a scalability issue with topologies adding blocks of session profiles?

 

To workaround we have to open the xml file and edit the session properties using a text editor.

 

Does this look like a bug and do any workarounds come to mind?

 

Thanks.

 

iTesttopology
EoX_Pivot_Load_Testbed.zip (5.6 KiB)
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
YujieL avatar image
YujieL answered YujieL posted

We will investigate. We have done performance measurements in house but did not find this problem.  Can you open the progress view while the refresh is happening?  How many refresh jobs are running and what does the message say in the progress view?

6 comments
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

mbarfiel avatar image mbarfiel commented ·

I made some changes on the topology and you get a "Refresh iTest Explorer". A dialog box shows the process and it looks like the workspace is building after every change.

 

This process takes over and you have to wait until it finishes to move forward. It looks like iTest is ambitious to rebuild the workspace after every change. This probably needs throttled back to rebuild after the file is saved.

 

Does this help?

0 Likes 0 ·
IvanS avatar image IvanS mbarfiel commented ·

We had this problem in iTest 4.0. It was fixed in iTest 4.0.1 release. What iTest version are you using?

0 Likes 0 ·
mbarfiel avatar image mbarfiel IvanS commented ·

We are using iTest 4.0.2, Build 52893.

0 Likes 0 ·
IvanS avatar image IvanS mbarfiel commented ·

Thanks for sample files. I was able to reproduce the issue.

If it's critical for you please work with Fanfare support.

Otherwise this will be fixed in future bug fix release.

0 Likes 0 ·
AmishP avatar image AmishP mbarfiel commented ·

Hi Mike,

 

We are able to reproduce the issue in-house. We definitely will take a look into it deeper. Is this issue affecting a lot of people?

 

-A

0 Likes 0 ·
mbarfiel avatar image mbarfiel AmishP commented ·

I will put a support ticket in for this. We have a couple of test beds that have 100+ devices. This is impacting two of my testers right now.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.