public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alessandro Barbieri" <lssndrbarbieri@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: sys-process/iotop-c/
Date: Fri, 27 Mar 2020 18:15:13 +0000 (UTC)	[thread overview]
Message-ID: <1585332249.626e55e1aa2a23ccb8bd37ac0001a15b2483ea33.Alessandro-Barbieri@gentoo> (raw)

commit:     626e55e1aa2a23ccb8bd37ac0001a15b2483ea33
Author:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Fri Mar 27 18:04:09 2020 +0000
Commit:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
CommitDate: Fri Mar 27 18:04:09 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=626e55e1

sys-process/iotop-c: longdescription

Package-Manager: Portage-2.3.96, Repoman-2.3.21
Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>

 sys-process/iotop-c/metadata.xml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/sys-process/iotop-c/metadata.xml b/sys-process/iotop-c/metadata.xml
index 4cbc5f6..a17f7c6 100644
--- a/sys-process/iotop-c/metadata.xml
+++ b/sys-process/iotop-c/metadata.xml
@@ -6,8 +6,11 @@
 		<name>Arthur Zamarin</name>
 	</maintainer>
 	<longdescription lang="en">
-		Top-like UI used to show which process is using the I/O. Ported from the
-		Python language to C.
+Your Linux server is too slow or load is too high? One of the possible causes of such symptoms may be high IO (input/output) waiting time, which basically means that some of your processes need to read or write to a hard drive while it is too slow and not ready yet, serving data for some other processes.
+
+Common practice is to use iostat -x in order to find out which block device (hard drive) is slow, but such information is not always much helpful. It could help you much more if you knew which process reads or writes the most data from your slow disk, so you could possibly renice it using ionice or even kill it.
+
+IOTop will identify processes, which use high amount of input/output requests on your machine. It is similar to the well known top utility, but instead of showing you what consumes CPU the most, it lists processes by their IO consumption. Inspired by iotop python script from Guillaume Chazarain, but rewritten to C by Vyacheslav Trushkin so it now runs without python at all.
 	</longdescription>
 	<upstream>
 		<remote-id type="github">Tomas-M/iotop</remote-id>


             reply	other threads:[~2020-03-27 18:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 18:15 Alessandro Barbieri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-08 12:34 [gentoo-commits] repo/proj/guru:dev commit in: sys-process/iotop-c/ Arthur Zamarin
2021-05-03 14:49 Zamarin Arthur
2021-04-23 16:33 Zamarin Arthur
2021-04-23 16:33 Zamarin Arthur
2021-04-23 16:33 Zamarin Arthur
2021-03-24 14:28 Mathieu Tortuyaux
2021-01-29  6:45 Zamarin Arthur
2021-01-29  6:45 Zamarin Arthur
2020-10-12  6:26 Zamarin Arthur
2020-10-12  6:26 Zamarin Arthur
2020-09-02  5:27 Zamarin Arthur
2020-08-28  4:56 Zamarin Arthur
2020-04-09 19:47 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-04-09 13:34 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2019-04-10 17:17 Zamarin Arthur
2019-04-09 17:30 Zamarin Arthur

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=1585332249.626e55e1aa2a23ccb8bd37ac0001a15b2483ea33.Alessandro-Barbieri@gentoo \
    --to=lssndrbarbieri@gmail.com \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@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