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?