linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* swap behavior during fast allocation
@ 2013-08-05 18:04 Luigi Semenzato
  2013-08-05 18:24 ` Dave Hansen
  0 siblings, 1 reply; 3+ messages in thread
From: Luigi Semenzato @ 2013-08-05 18:04 UTC (permalink / raw)
  To: linux-mm

Greetings MM experts,

we (Chrome OS) are experiencing episodes of extremely sluggish
interactive response, i.e. tens of seconds delay between an action
(such as typing something) and the corresponding screen update during
times of very fast allocation, while using zram.

We can reproduce this by running a few processes that mmap large
chunks of memory, then randomly touch pages to fault them in.  We also
think this happens when a process writes a large amount of data using
buffered I/O, and the "Buffers" field in /proc/meminfo exceeds 1GB.
(This is something that can and should be corrected by using
unbuffered I/O instead, but it's a data point.)

We're wondering if this problem has been noticed before and what folks
do to ameliorate the situation.  Specifically, is there any way to
throttle the rate of allocation when the system is swapping?

Thanks!
Luigi

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: swap behavior during fast allocation
  2013-08-05 18:04 swap behavior during fast allocation Luigi Semenzato
@ 2013-08-05 18:24 ` Dave Hansen
  2013-08-05 18:30   ` Luigi Semenzato
  0 siblings, 1 reply; 3+ messages in thread
From: Dave Hansen @ 2013-08-05 18:24 UTC (permalink / raw)
  To: Luigi Semenzato; +Cc: linux-mm

On 08/05/2013 11:04 AM, Luigi Semenzato wrote:
> We can reproduce this by running a few processes that mmap large
> chunks of memory, then randomly touch pages to fault them in.  We also
> think this happens when a process writes a large amount of data using
> buffered I/O, and the "Buffers" field in /proc/meminfo exceeds 1GB.
> (This is something that can and should be corrected by using
> unbuffered I/O instead, but it's a data point.)

Where are all the buffers coming from?  Most I/O to/from filesystems
should be instantiating relatively modest amounts of Buffers.  Are you
doing I/O directly to devices for some reason?

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: swap behavior during fast allocation
  2013-08-05 18:24 ` Dave Hansen
@ 2013-08-05 18:30   ` Luigi Semenzato
  0 siblings, 0 replies; 3+ messages in thread
From: Luigi Semenzato @ 2013-08-05 18:30 UTC (permalink / raw)
  To: Dave Hansen; +Cc: linux-mm

On Mon, Aug 5, 2013 at 11:24 AM, Dave Hansen <dave.hansen@intel.com> wrote:
> On 08/05/2013 11:04 AM, Luigi Semenzato wrote:
>> We can reproduce this by running a few processes that mmap large
>> chunks of memory, then randomly touch pages to fault them in.  We also
>> think this happens when a process writes a large amount of data using
>> buffered I/O, and the "Buffers" field in /proc/meminfo exceeds 1GB.
>> (This is something that can and should be corrected by using
>> unbuffered I/O instead, but it's a data point.)
>
> Where are all the buffers coming from?  Most I/O to/from filesystems
> should be instantiating relatively modest amounts of Buffers.  Are you
> doing I/O directly to devices for some reason?

Correct.  This is the autoupdate process, which writes the changed
kernel and filesystem blocks directly to raw partitions.  (The
filesystem partition is obviously not currently in use.)

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-08-05 18:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-05 18:04 swap behavior during fast allocation Luigi Semenzato
2013-08-05 18:24 ` Dave Hansen
2013-08-05 18:30   ` Luigi Semenzato

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox