Odd graph intervals?

[jon_iz]

This may have been asked before...
Maybe it's always done this and I've not noticed before?

Looking at the charts and trend graphs, I have noticed that they seem to update at 1 minute intervals both locally on the pages served by CMX and on my website, uploaded by ftp.
Logging interval is set to 10 minutes, FTP upload is 10 minutes and realtime is 5 secs. graph hours 168, graph days 31
This can be seen in the attached graph, when cumulus was restarted a little after 1520 today.

Capture.PNG

If I restart CMX, it seems to revert back to 10 minute intervals prior to the point of restart.
It seems to be the same whatever device/browser i view it on, so my first question is, Why does it do this, is it related to data held in memory rather extracted from logfiles?

What triggered this for me today was an email from by webhost advising me that I was about to hit a traffic quota for my website, and when I looked, CMXhad generated 4.6GB of ftp traffic for the last 3 weeks.
Initially I put it down to adding a webcam image every 10 minutes, until I looked at some of the files going up, I discovered that many were 100's of KB. Dropping the sizes into a spread sheet, it looks like it has certainly ramped up. (The webcam image wasn't even scratching the surface of what was going up - tempdata.json was 839KB)

So, in order to preserve throughput, I increased the davis logger interval to 15 minutes, (which cleared it) and the associated settings in CMX, then changed my mind and put it back to 10 minutes and spoke to the host, who removed the traffic restriction.
Since then, I looked at the files going up and they have dropped in size, to about 25% of what they were. But now I am paying attention, I have noticed the effects with the graphs come and go.

So, my second question is, do the json file sizes relate to the data gathered while cumulus is running, to a maximum governed by graph hours/days settings, but it is reset and read from logs (at defined log interval) if restarted?

[Mapantz]

Regarding your first point; That's normal after restarting Cumulus MX. It loads the prior data at your logger / cumulus interval, because there's no 1 minute log data. When CMX is running again, it'll log at 1 minute intervals again, as it''ll be reading the realtime.txt.

[mcrossley]

A correct summary there. You get 1 minute data whilst MX is running. On start-up it prepopulates the JSON with data from you log records (at whatever interval that may be).
Once running the log interval data is gradually replaced with the one minute data.

The next release will alleviate this a bit as you will be able to choose what data is included in the tempdata.json file, so you will be able to drop data series you may not be interested in.