I must be stupid but I cannot fathom how 24.67GB + 10.19GB can be less than 24.06GB + 9.98GB.
Bug?
Also the points on the graph are slightly skewed from their respective x axis markings.
Hi @Storgeez,
Line smoothing can cause the display anomaly you see. Iāve seen similar on my node before. Quite a few updates ago the actual ādotā or point on the graph stopped showing for me, but it looks to be on the correct x-axis location in Chrome.
Forcing the point to show using scroll wheel:
1 Like
The incorrect graph points are a feature? Classic!
Iāve never actually seen the dot, scroll wheel only scrolls the page in Chrome for meā¦
I think the numbers also donāt take account of deletes.
To be clear, the graph is correct, but your perception is the x-axis points are skewed and the line is incorrect.
This example in Excel shows why the points and smoothed line are correct, but a lack of vertical gridlines or visible points create the above perception:
6 Likes
Youāre right, the points on the graph are fine, they just need to fix the artificial points when you mouse over them to make them obvious. Now that you explained this, the offset x axis wasnāt offset actually but is accurate, I was thinking that because the local extremes on the graph were located offset from the data points, but as you explained, this is due to interpolation.
By ācorrectā I assume you mean the points only or that it looks nice only but is incorrect, because the interpolated sections are blatantly wrong. The use of sin(x)/x interpolation is completely wrong for data graphs like this, itās good for sinewaves but graphs are nearly always not sinewaves, itās a bad approximation for this use case. Also misleading as we can see, lol. But they do look āniceā when you donāt care about the data, jagged edges are ugly.
Looks like body is too similar to what was recently posted but no longer is.