public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paul at preney dot ca" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/27735] New: memusagestat with GiB or TiB of RAM axis values can be clipped Date: Thu, 15 Apr 2021 17:50:44 +0000 [thread overview] Message-ID: <bug-27735-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27735 Bug ID: 27735 Summary: memusagestat with GiB or TiB of RAM axis values can be clipped Product: glibc Version: 2.33 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: paul at preney dot ca CC: drepper.fsp at gmail dot com Target Milestone: --- Created attachment 13371 --> https://sourceware.org/bugzilla/attachment.cgi?id=13371&action=edit memusagestat-large-values.patch Using memusagestat with collected data from systems that have of GiB of RAM or more can result in the heap axis' values being clipped since they are too large/long for the space provided. Additionally such values should be abbreviated using G (for giga) and T for (tera) and scaled as the other values are. The requires the _scale values to be declared as site_t (or some type larger than int) and ULL used with the constant values (e.g., 100ULL * 1024 * 1024 * 1024, etc.) so they result in not-always-false if tests. While cosmetic, I have also adjusted the colour values which were too bright against the bright grey (almost white) background to provide more contrast. I also made the background colour not transparent since it can make the graph very hard-to-read on non-white underlying backgrounds. I avoided making any other changes. (The colours and transparency changes are simple edits involving 4 lines of code.) ASIDE: I colour shifted the blue to be a dark cyan to allow it to be more easily seen as different from black. Pure blue is harder to see unless bright --but when bright it is harder to see against the background. These changes can be seen in the attached patch file: memusagestat-large-values.patch . :-) (While I used v2.33 this affects all versions of glibc with memusagestat.) -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-04-15 17:50 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 17:50 paul at preney dot ca [this message] 2021-04-15 17:51 ` [Bug libc/27735] " paul at preney dot ca
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-27735-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).