From: arlie@worldash.org (Arlie Stephens)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Work (really slow directory access on ext4)
Date: Wed, 30 Jul 2014 10:38:13 -0700 [thread overview]
Message-ID: <20140730173813.GA781@worldash.org> (raw)
In-Reply-To: <CAPDOMVgTUC+_9SWBDk-CVGTcJAqHL_08FOE0Q6yFHhYzfUXdmQ@mail.gmail.com>
Hi Nick,
On Jul 29 2014, Nick Krause wrote:
> >> I was doing a vanilla ls. So was the original reporter, unless he has
> >> some really strange aliases.
> >>
> >>
> >> I'm afraid I'll be rather unpopular if I drop the caches on the system
> >> in question, creating a burst of poor performance, so my best bet is
> >> probably to see what I can do with ftrace on Monday, or perhaps
> >> partway through the weekend.
> >>
> >> There is normally a fair amount of disk activity going on - much of it
> >> writes. So I can expect cached blocks to age out in a reasonable time.
> >>
> > Arlie,
> > Whenever you get around to it is fine.
> > Just send me a log.
> > Cheers Nick
>
> Arlie,
> just a friendly reminder can you try to send me the log this week.
> Regards Nick
I was just going to post an apology for going dark on you. I made one
attempt to capture the data yesterday, and messed up - no useful data
saved. And then half the world invaded my workspace with higher
priority tasks ;-)
I'm going to make another attempt at it this morning.
On the good side, Vladis' observations of his mail directory have been
a great help. Now I know that simply being a large ext4 directory is
not the problem ;-) I.e. ext4 really isn't as brain damaged as I
feared. (We had someone here who was initially sure that was it, and
he has more experience in linux server space than I do, so I took his
initial opinion at face value.)
More soon, I hope.
--
Arlie
(Arlie Stephens arlie at worldash.org)
next prev parent reply other threads:[~2014-07-30 17:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 16:38 Work Nick Krause
2014-07-24 16:43 ` Work Kristofer Hallin
2014-07-24 16:44 ` Work Lucas Tanure
2014-07-24 16:47 ` Work Nick Krause
2014-07-26 21:13 ` Work Yi Li
2014-07-26 21:55 ` Work Lucas Tanure
2014-07-24 16:51 ` Work Andev
2014-07-24 17:10 ` Work Nick Krause
2014-07-25 2:23 ` Work Nick Krause
2014-07-25 5:33 ` Work ravi ranjan Mishra
2014-07-25 11:44 ` Work Lucas Tanure
2014-07-25 12:17 ` Work Robert P. J. Day
2014-07-25 15:19 ` Work Nick Krause
2014-07-25 17:18 ` Work Robert P. J. Day
2014-07-25 17:28 ` Work Valdis.Kletnieks at vt.edu
2014-07-25 17:42 ` Work Valdis.Kletnieks at vt.edu
2014-07-25 21:54 ` Work Nick Krause
2014-07-25 22:23 ` Work Arlie Stephens
2014-07-25 23:02 ` Work Nick Krause
2014-07-25 23:35 ` Work Valdis.Kletnieks at vt.edu
2014-07-25 23:44 ` Work Nick Krause
2014-07-26 1:08 ` Work (really slow directory access on ext4) Arlie Stephens
2014-07-26 1:22 ` Nick Krause
2014-07-30 2:34 ` Nick Krause
2014-07-30 17:38 ` Arlie Stephens [this message]
2014-07-30 19:48 ` Valdis.Kletnieks at vt.edu
2014-07-30 20:45 ` Nick Krause
2014-07-31 23:36 ` Arlie Stephens
2014-07-31 23:41 ` Henry Hallam
2014-08-01 1:47 ` Nick Krause
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 14:49 Theodore Ts'o
2014-08-06 18:26 ` Arlie Stephens
2014-08-06 19:29 ` Nick Krause
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=20140730173813.GA781@worldash.org \
--to=arlie@worldash.org \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.