Symantec anti virus problems updating remote
Most users get a similar result to their "favourite" speed test or the ISP "recommended" speed test.
Networks are comparatively slow compared to local disks, and certainly not reliable, so you’re bound to end up with locked file conflicts and would be lucky if data wasn’t corrupted from time to time.Most sites you use online will have a higher ping time.Unless you have 500 megabit to 1gigabit , you should be able to ignore ping time and still test your line to maximum speed. This is a browser based speed test, and needs some temporary memory to store the incoming data before it can free it.As the file gets bigger and the number of users grows, the problem gets worse exponentially.The standard Sage solution seems to be to tell people their hardware in inadequate whenever timeouts occur.In fact it’s in Sage’s interests to keep Line 50 running slower than a slug in treacle.
Line 50 is the cheap end of the range – if it ran at a decent speed over a network, multi-user, people wouldn’t buy the expensive Line 200 (aka MMS).
In speed test preferences you can set a maximum memory use, for example 10, for 10 megabytes.
The test will then use much less memory but it may not drive a connection to full speed.
Because browsers typically download files and store them on disk the upper limit of this speed test is going to be limited by the fastest write speed of your PC disk drive.
In the case of a spinning disk this might be as low as 500 megabit.
If you are interested in ping time to all different locations, the speed test has a latency radar plot. Although it tries not to exceed the limitations of your mobile device, it might.