I have a little problem with the update datas of the steelseries Gauges, i set 3 seconds on real time in Cumulus and of the server but datas will be update every 8 seconds, 20 seconds, 30 seconds on my web site, it depends...

Every so often you get a 'corrupt' realtimegauges.txt file, the only thing wrong with it is that the closing "}" at the end of the file is missing for some reason - possibly because the file is being written to at the time of read. I have put a workaround in for that on my site by creating the JSON data using PHP and waiting for the realtimeGuages.txt file to be flagged as updated on the web server file system (long polling).

I see you have based your gauges on the 'test' script I have on my site, that version has not yet been released and does contain a couple of bugs that I know about but have yet to fix.

Every so often you get a 'corrupt' realtimegauges.txt file, the only thing wrong with it is that the closing "}" at the end of the file is missing for some reason - possibly because the file is being written to at the time of read. I have put a workaround in for that on my site by creating the JSON data using PHP and waiting for the realtimeGuages.txt file to be flagged as updated on the web server file system (long polling).

I see you have based your gauges on the 'test' script I have on my site, that version has not yet been released and does contain a couple of bugs that I know about but have yet to fix.

I would say the difference is your host provider's FTP is not capable of uploading a quite large file like realtimegauges.txt every 3 seconds. Even your friends if you look at it does not change every 3 seconds, the readings stay static sometimes for as many as 3 or 4 timings i.e. 9-12 seconds.

I would have thought a more realistic timing would be 10 seconds, as I am sure that Mark didn't design the gauges to be almost "realtime" gauges otherwise he wouldn't have set the default countdown to 60 seconds.

It's taking about 6 or 7 seconds to get the realtime files to your server, then there is a short gap until the next realtime upload slot comes around, so your uploads are typically around 8 or 9 seconds apart. You're already using the rename option, and that should minimise the problem where the file is incomplete on the server. From the log, it's clear that the rename takes a fraction of a second

So the limit is on the speed that the files can be uploaded to your server. You could reduce the realtime upload interval to 1 second, and then the next slot will come around more quickly, but that will only get you down to 6 or 7 seconds. Or, more realistically, increase it to 10 seconds, say, as was suggested earlier.

I don't know why the gauges code is apparently getting incomplete files as Mark saw; the rename takes a fraction of a second, so you wouldn't expect the file to be unavailable for very long at all.

I've just had a look at the realtime.txt file on your site, and constantly refreshing the file in my browser. I can see the same thing that Mark noted; that it's only updating every 30 seconds or so. Assuming that it's still being uploaded every 8 or 9 seconds, then as Mark said, there must be some kind of caching issue with your server such that it's only sending the latest version of the file every 30 seconds or so, even though a newer version has been uploaded.