View Issue Details

IDProjectCategoryView StatusLast Update
0000075SpeedFanLogging and chartingpublic2005-03-24 21:26
ReporterThomas Assigned Toalfredo  
PrioritynormalSeverityminorReproducibilityalways
Status acknowledgedResolutionopen 
PlatformPCOSWindowsOS VersionXP SP2
Product Version4.15 
Summary0000075: Charts include suspend times
DescriptionWhen the PC is suspended and later on resumed, the time while it was suspended is shown as large gap in the charts. The longer the suspend period was, the more unreadable are the charts. See picture.
Steps To ReproduceSuspend and resume later on.
TagsNo tags attached.
Motherboard Model
Video Card Model

Activities

2004-08-25 22:24

 

SpeedFan Chart.PNG (19,053 bytes)   
SpeedFan Chart.PNG (19,053 bytes)   

alfredo

2004-08-30 09:19

manager   ~0000295

Which workaraound would you suggest? Zeroing stats upon resume from suspend?

Thomas

2004-08-30 17:07

reporter   ~0000296

I would prefer to have the suspended time "missing" from the diagram. So the chart would look like the chart before suspend, followed with the data after suspend. If possible, a vertical line to indicate the suspend event would be nice.
(I would like to see the data before and after suspend in the same diagram for comparison.)

flachschippe

2005-03-20 23:47

reporter   ~0000790

Similar to 229, I'd suggest to not draw anything when you do not have data. Here, this could mean, as Thomas already suggested, to omit the suspend interval from the chart, and to draw a one-pixel vertical marker instead.

coldmist

2005-03-24 21:26

reporter   ~0000792

I've requested this once or twice myself (privately via email and once on this forum, if memory serves). I got the same reply from Alfredo then too. ;)

Depending on how your data is stored and how your graphing code is set up, you might not have a timestamp for each data point. From the way the graphing code responds to various situations (like showing hard drive temps with slower samples with mboard temps), I would assume that you just have a FIFO array and just pass it to the graphing routine at each sample period. The graphing routine is just showing what the data has and does the best it can. I would assume you would have to add more data to keep track of timestamps per sample slice than you do now.

The simplest approach might be to offer an option to just clear the entire history when the previous sample point is older than 5 minutes ago. I would even go for that. Just so the graph has something useful during the first 11 minutes of uptime. Then, all you have to store is the last sample point graphed and compare 'now' with that.

Just an idea.

Issue History

Date Modified Username Field Change
2004-08-25 22:24 Thomas New Issue
2004-08-25 22:24 Thomas File Added: SpeedFan Chart.PNG
2004-08-30 09:19 alfredo Note Added: 0000295
2004-08-30 09:19 alfredo Status assigned => acknowledged
2004-08-30 17:07 Thomas Note Added: 0000296
2005-03-20 23:47 flachschippe Note Added: 0000790
2005-03-24 21:26 coldmist Note Added: 0000792