After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618781 - Use a C1-continuous curve for the graph
Use a C1-continuous curve for the graph
Status: RESOLVED DUPLICATE of bug 568985
Product: system-monitor
Classification: Core
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-16 11:42 UTC by Chris Wilson
Modified: 2012-09-28 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Improved load-graph (12.84 KB, patch)
2010-05-16 11:42 UTC, Chris Wilson 		none Details | Review

Description Chris Wilson 2010-05-16 11:42:41 UTC 
Created attachment 161159 [details] [review]
Improved load-graph

Currently the graph is only C0-continuous with smooth weights between points resulting in quite a bouncy graph. We can improve this by keeping the derivatives the same between points so that the curve becomes much smoother and more indicative of change in load.
Comment 1 Robert Roth 2012-08-08 18:42:24 UTC 
Could you please attach a sample screenshot with your improved C1-continuous loadgraphs, and maybe an updated patch? I really like the idea, and the old patch also looks promising, mainly because right now lot of processing time is spent with drawing the curves, and with your patch that is simplified in some cases to a simple line (e.g memory usage does not change often, that would most probably make use of this).
Comment 2 Robert Roth 2012-09-28 18:40:41 UTC 
I think this is the same as bug 568985, making the load graph smoother, thus I am marking this as a duplicate. 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 568985 ***