From: Pekka Enberg <penberg@kernel.org>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>, Jens Axboe <jaxboe@fusionio.com>,
Wu Fengguang <fengguang.wu@intel.com>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: slow performance on disk/network i/o full speed after drop_caches
Date: Wed, 24 Aug 2011 09:20:07 +0300 [thread overview]
Message-ID: <CAOJsxLEFYW0eDbXQ0Uixf-FjsxHZ_1nmnovNx1CWj=m-c-_vJw@mail.gmail.com> (raw)
In-Reply-To: <4E5494D4.1050605@profihost.ag>
On Wed, Aug 24, 2011 at 9:06 AM, Stefan Priebe - Profihost AG
<s.priebe@profihost.ag> wrote:
> i hope this is the correct list to write to if it would be nice to give me a
> hint where i can ask.
>
> Kernel: 2.6.38
>
> I'm seeing some strange problems on some of our servers after upgrading to
> 2.6.38.
>
> I'm copying a 1GB file via scp from Machine A to Machine B. When B is
> freshly booted the file transfer is done with about 80 to 85 Mb/s. I can
> repeat that various times to performance degrease.
>
> Then after some days copying is only done with about 900kb/s up to 3Mb/s
> going up and down while transfering the file.
>
> When i then do drop_caches it works again on 80Mb/s.
>
> sync && echo 3 >/proc/sys/vm/drop_caches && sleep 2 && echo 0
>>/proc/sys/vm/drop_caches
>
> Attached is also an output of meminfo before and after drop_caches.
>
> What's going on here? MemFree is pretty high.
>
> Please CC me i'm not on list.
Interesting. I can imagine one or more of the following to be
involved: networking, vmscan, block, and writeback. Lets CC all of
them!
> # before drop_caches
>
> # cat /proc/meminfo
> MemTotal: 8185544 kB
> MemFree: 6670292 kB
> Buffers: 105164 kB
> Cached: 166672 kB
> SwapCached: 0 kB
> Active: 728308 kB
> Inactive: 567428 kB
> Active(anon): 639204 kB
> Inactive(anon): 394932 kB
> Active(file): 89104 kB
> Inactive(file): 172496 kB
> Unevictable: 2976 kB
> Mlocked: 2992 kB
> SwapTotal: 1464316 kB
> SwapFree: 1464316 kB
> Dirty: 52 kB
> Writeback: 0 kB
> AnonPages: 1026920 kB
> Mapped: 54208 kB
> Shmem: 8380 kB
> Slab: 80724 kB
> SReclaimable: 22844 kB
> SUnreclaim: 57880 kB
> KernelStack: 2872 kB
> PageTables: 35448 kB
> NFS_Unstable: 0 kB
> Bounce: 0 kB
> WritebackTmp: 0 kB
> CommitLimit: 5557088 kB
> Committed_AS: 6187972 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed: 292360 kB
> VmallocChunk: 34359425327 kB
> HardwareCorrupted: 0 kB
> DirectMap4k: 5632 kB
> DirectMap2M: 2082816 kB
> DirectMap1G: 6291456 kB
>
> # cat /proc/meminfo
> MemTotal: 8185544 kB
> MemFree: 6888060 kB
> Buffers: 372 kB
> Cached: 61492 kB
> SwapCached: 0 kB
> Active: 659156 kB
> Inactive: 426664 kB
> Active(anon): 638892 kB
> Inactive(anon): 395200 kB
> Active(file): 20264 kB
> Inactive(file): 31464 kB
> Unevictable: 2976 kB
> Mlocked: 2992 kB
> SwapTotal: 1464316 kB
> SwapFree: 1464316 kB
> Dirty: 0 kB
> Writeback: 0 kB
> AnonPages: 1026952 kB
> Mapped: 54236 kB
> Shmem: 8316 kB
> Slab: 70616 kB
> SReclaimable: 12264 kB
> SUnreclaim: 58352 kB
> KernelStack: 2864 kB
> PageTables: 35448 kB
> NFS_Unstable: 0 kB
> Bounce: 0 kB
> WritebackTmp: 0 kB
> CommitLimit: 5557088 kB
> Committed_AS: 6187932 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed: 292360 kB
> VmallocChunk: 34359425327 kB
> HardwareCorrupted: 0 kB
> DirectMap4k: 5632 kB
> DirectMap2M: 2082816 kB
> DirectMap1G: 6291456 kB
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2011-08-24 6:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E5494D4.1050605@profihost.ag>
2011-08-24 6:20 ` Pekka Enberg [this message]
2011-08-24 9:01 ` Stefan Priebe - Profihost AG
2011-08-24 9:33 ` Wu Fengguang
2011-08-25 9:00 ` Stefan Priebe - Profihost AG
2011-08-26 2:16 ` Wu Fengguang
2011-08-26 2:54 ` Stefan Priebe - Profihost AG
2011-08-26 3:03 ` Wu Fengguang
2011-08-26 3:13 ` Stefan Priebe
2011-08-26 3:26 ` Wu Fengguang
2011-08-26 3:30 ` Zhu Yanhai
2011-08-26 6:18 ` Stefan Priebe - Profihost AG
2011-08-31 7:11 ` Stefan Priebe - Profihost AG
2011-09-01 4:14 ` Wu Fengguang
2011-09-01 5:41 ` Stefan Priebe - Profihost AG
2011-09-01 12:57 ` Mel Gorman
2011-08-24 9:32 ` Wu Fengguang
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='CAOJsxLEFYW0eDbXQ0Uixf-FjsxHZ_1nmnovNx1CWj=m-c-_vJw@mail.gmail.com' \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=netdev@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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