Posted by Grant Foraker on September 22, 2011 at 13:33:07: Uploaded files: 2
A customer was getting complaints from their office in WA about slow speed and interrupts in CometAnywhere. Since I couldn't find a diagnostic tool to do a timing check, I wrote CAWCHK.IBS.
Per Brian's suggestion, the program uses (GetSessionID) to make the CAW client PC do something each iteration. You run it once to get an idea of what the "normal" iteration time is and then run it again to see how stable the line conditions are.
The program will scroll each iteration down the screen and will run for 300 seconds (5 minutes) and stop itself. F3 will also stop it. The program displays a bar chart based on how far off "normal" the line conditions were. I made the presumption that +/- 20% is not a bother to the operator. People get used to "normal". However, if the line is + 21-40% I flag the iteration in yellow. Over +40% is flagged in red. Blue for 20% below "normal". See the screen shot.
It worked out as a test program. I was able to use it to absolve CometAnywhere as the problem. CAWCHK ran with much better speed locally and from three other remote locations. The furtherst being HI. The ISP and their local IT guy are now testing the WA LAN and Internet connection.
--------------------------------------------------------------------
But, while testing I was suprised that CAW had more overhead than I thought.
Method Timing (ms) Ping Comet
--------------------------------------------------------
Standalone Comet 20 n/a 16
Inside LAN 212 1 32
Outside 1 263 24 16
Outside 2 239 25 16
Outside 3 310 n/a 32
--------------------------------------------------------
All locations running Comet448
Can CAW be made faster?
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.