it is so nice to have your feedback. That is a very impressive points count.
I am glad it works out for you. I would say the SSD definitely helped a lot as well.
The spec of your server is not too hard to obtain anyway which is good.
Did you use the Windows Service (auto startup) component mentioned in Mango's help instructions?
I am curious how you tested it with a second PC before you upgraded the system.
I am guessing that you ran both PCs at the same time since all your DSs are IP based.
You should write a user-case for the forum 'Stories' section as well. that will be nice.
We have explored adding the ability to set event detectors to not raise the event more than once in some amount of time, but that feature was not merged in at the time so hasn't become part of Mango yet.
I think what you're requesting would be something like that, but for data source events, which is a good idea if it is a good idea to do it for event detectors.
This is probably only a display issue. I would guess above that on the page it is showing the value for hour 23 as the current value, and that if you chart it for the day you will see the values in the chart. Thanks for bringing this to our attention!
PS I would recommend you to try a different browser but I don't think it will make any difference as Apple in its infinite wisdom prohibits using anything than its own Safari browser engine on iOS, so Chrome on on iOS is a basically a skinned version of Safari.
It means that for 26 points there was more data already on the receiving end than data on the publisher's side for the period checked. Usually this is caused by a point with interval logging on the publisher transmitting its realtime updates as opposed to logged events, then the receiver's default point logs all data if the receiver is configured to save real time data, and that amounts to an overcount. It can be possible other ways (disk getting full, importing extra data at receiver, etc), but that's what I'd guess caused it here. The solution to prevent it if that is the cause would be to change your publisher's publish event to logged data instead of updates.