Bug 434041

Summary: Labels in memory overview overlap and curve is wrong at the start
Product: [Applications] plasma-systemmonitor Reporter: Nicolas Werner <nicolas.werner>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED DUPLICATE    
Severity: minor CC: ahiemstra, plasma-bugs
Priority: NOR    
Version: 5.21.2   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Screenshot of graph

Description Nicolas Werner 2021-03-06 02:44:33 UTC
Created attachment 136424 [details]
Screenshot of graph

SUMMARY

When opening the memory use history initially, it for some reason overlapped the labels of swap and memory use?

Also the line starts out very weirdly. The memory usage profile was flat for the last 10 hours, but the widgets shows a few weird jumps in the beginning. This is probably related to the smoothing?

All of that fixes itself after waiting for a bit and/or switching tabs.

STEPS TO REPRODUCE
1. Open system monitor
2. Go to history tab

OBSERVED RESULT

See intro

EXPECTED RESULT

Labels don't overlap and curve goes smoothly or sharply from 0 to 53 instead of wiggling at the start and end.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Comment 1 Nicolas Werner 2021-03-06 02:46:56 UTC
Woops, this is probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=429156
Comment 2 Arjen Hiemstra 2021-03-08 11:27:47 UTC

*** This bug has been marked as a duplicate of bug 429156 ***
Comment 3 Arjen Hiemstra 2021-03-08 11:30:39 UTC
> Also the line starts out very weirdly. The memory usage profile was flat for the last 10 hours, but the widgets shows a few weird jumps in the beginning. This is probably related to the smoothing?

This is an unfortunate artifact of the smoothing algorithm that doesn't deal well with rapid changes in value. Unfortunately it's all a tradeoff since there are ways to avoid the spikes but those cause other issues. Right now the algorithm at least matches what other chart libraries out there do.