The only variable here is the network link, so I did a quick check on network throughput and transferred a 213 MB file in around 6 seconds using windows copy from my mounted samba share in Colorado to my desktop here in silicon valley.
I suspect this is something to do with Zeus not liking this particular network
Many years ago I remember getting reports of Zeus running slow over one particular third party network system and also one on Samba networks.
I don't think I every really go to the bottom of this issue, even after setting up a test Samba network, which worked fine for me.
This always confused me as Zeus uses nothing but stock standard Win32 and C library calls for all it's file handling.
I put this down to the fact that Zeus does a lot of checking of the file status and on some networks, for reason that I don't fully understand, this can be slow.
From the trace I can see the three second switching time:
Code: Select all
[Fri Oct 27 11:09:12 2017] RUNTIME "xpWorkspaceEx.cpp" (4912) >> Workspace::load started.
[Fri Oct 27 11:09:15 2017] RUNTIME "xpWorkspaceEx.cpp" (4917) >> Workspace::load complete.
This part of the load was also slow:
Code: Select all
[Fri Oct 27 11:08:32 2017] RUNTIME "xpWorkspaceEx.cpp" (3866) >> Workspace::load started.
[Fri Oct 27 11:08:36 2017] RUNTIME "xpWorkspaceEx.cpp" (3907) >> Workspace::sort(1)
Mapping the trace output to the code, I can see this also looks like the network issue mentioned above.
The code that is running is doing nothing more than hitting the file system for file status information.
The switch focus slow down is caused by Zeus rebuilding the workspace tree.
To build the tree it does a status check for each of the files, checking if the file status has changed or the file has been deleted.
So it is those 500 status checks that are causing this slow down.
To confirm this theory can you run this simple test.
Start Zeus with the workspace open.
From the toolbar click on the Navigator Toggle button (9th button from the left) to hide the navigator panel.
Move the focus away and then back to Zeus and you should now see the response will be instant.
With the navigator not showing the tree is not loaded and none of these file status requests takes place.
I will do some investigation into this.
PS: Could you repeat the test with the new Zeus version found here: http://www.zeusedit.com/z300/z-beta.zip
This version implements a different version of the file access
Could you check to see if that make any difference