From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kde-apps/kde-l10n-16.04.3:5/5::gentoo conflicting with kde-apps/kdepim-l10n-15.12.3:5/5::gentoo
Date: Tue, 9 Aug 2016 12:50:08 -0500 [thread overview]
Message-ID: <c2d3d41d-c56a-9dca-badf-3ff79ba61ff2@verizon.net> (raw)
In-Reply-To: <3DB342B6-5CC0-41C4-98AE-8F07A44A623D@antarean.org>
On 08/09/2016 09:06 AM, J. Roeleveld wrote:
> On August 9, 2016 4:13:31 PM GMT+02:00, james <garftd@verizon.net> wrote:
>> AS a side note, I put 32G of ram on my system and still at times it is
>> laggy with little processor load and htop shows little <30% ram usage.
>> What tools do you use to track down mem. management issues?
>>
>> Any specific kernel tweaks?
> Try iotop....
OK, so the gentoo wikis says the only kernel modes for iotop are
General setup
-> CPU/Task time and stats accounting
[*] Enable extended accounting over taskstats
[*] Enable per-task storage I/O accounting
Do you add any others? Do you build a specific kernel for these sorts of
low level account and debug codes to work, as reading about, some
can cause noticable performance degredations. So do you have a special
kernel to track these problem and then return to a production kernel,
or leave them in all the time?
curiously,
James
next prev parent reply other threads:[~2016-08-09 16:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 15:02 [gentoo-user] kde-apps/kde-l10n-16.04.3:5/5::gentoo conflicting with kde-apps/kdepim-l10n-15.12.3:5/5::gentoo Michael Mol
2016-08-08 16:52 ` Alan McKinnon
2016-08-08 17:20 ` Michael Mol
2016-08-08 20:45 ` Alan McKinnon
2016-08-09 7:52 ` Peter Humphrey
2016-08-09 8:03 ` Neil Bothwick
2016-08-09 8:11 ` Peter Humphrey
2016-08-09 8:50 ` Alan McKinnon
2016-08-09 11:20 ` Peter Humphrey
2016-08-09 12:42 ` Michael Mol
2016-08-09 14:13 ` james
2016-08-09 14:06 ` J. Roeleveld
2016-08-09 17:50 ` james [this message]
2016-08-09 14:17 ` Michael Mol
2016-08-09 18:23 ` james
2016-08-09 18:41 ` Michael Mol
2016-08-09 22:22 ` james
2016-08-10 12:45 ` Michael Mol
2016-08-10 15:13 ` james
2016-08-10 15:20 ` Michael Mol
2016-08-10 19:47 ` james
2016-08-09 16:09 ` Daniel Frey
2016-08-09 18:43 ` Alan McKinnon
2016-08-09 18:44 ` Michael Mol
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=c2d3d41d-c56a-9dca-badf-3ff79ba61ff2@verizon.net \
--to=garftd@verizon.net \
--cc=gentoo-user@lists.gentoo.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: link
Be 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