From: Wu Fengguang <fengguang.wu@intel.com>
To: Satish Eerpini <eerpini@gmail.com>
Cc: Rik van Riel <riel@redhat.com>, Ray Lee <ray-lk@madrabbit.org>,
Christoph Lameter <cl@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: unresponsiveness on linux desktop during file copy
Date: Sun, 17 May 2009 20:17:11 +0800 [thread overview]
Message-ID: <20090517121711.GA3583@localhost> (raw)
In-Reply-To: <93655eb70905170501q3caf04acj761ff61b539b7d40@mail.gmail.com>
On Sun, May 17, 2009 at 08:01:29PM +0800, Satish Eerpini wrote:
> > Hmm, how do you define/feel the unresponsiveness? Is it related to
> > the currently *running* applications, or opening a *new* application?
>
> the unresponsiveness is for both the currently running applications
> and for opening new applications, here are some pointers :
>
> --> during normal operation, swtiching between windows( alt+tab) is
> simultaneous, while during a file copy it takes around 1 second, which
> I think is quite a lag.
> --> Opening a simple application like gnome-terminal takes a second or
> more for sure when there is a file copy going on.
> -->Also a particular window after gaining focus takes a second or so,
> to resume what it was doing, .. so if I am copying a file in a session
> of gnome-terminal and open another session of gnome-terminal and type
> in "clear" it takes around 2 seconds before the screen is cleared on
> the second session,
The clear command can be a big clue. Can you try these commands in the
terminal and show us the two log files?
strace -o all.log -T clear
strace -o sum.log -c clear
> this is the case with almost every application and worser with big
> ones like firefox and office. This was the kind of unresponsiveness I
> was talking about.
>
> Cheers
> Satish
> --
> http://satish.playdrupal.com
next prev parent reply other threads:[~2009-05-17 12:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 17:07 unresponsiveness on linux desktop during file copy Satish Eerpini
2009-05-15 17:12 ` Mark Knecht
[not found] ` <93655eb70905151024o634f8432j6c3db85df1f6ddfc@mail.gmail.com>
[not found] ` <5bdc1c8b0905151120p5aa58318t1765544fbbb695b2@mail.gmail.com>
2009-05-16 2:38 ` Satish Eerpini
2009-05-16 2:47 ` Mark Knecht
2009-05-16 3:12 ` Satish Eerpini
2009-05-16 3:37 ` Mark Knecht
2009-05-16 6:52 ` Satish Eerpini
2009-05-16 21:11 ` Mark Knecht
2009-05-17 8:54 ` Robert Hancock
2009-05-17 9:04 ` Satish Eerpini
2009-05-17 8:52 ` Robert Hancock
2009-05-15 18:02 ` Ray Lee
2009-05-15 19:33 ` Christoph Lameter
2009-05-16 16:03 ` Ray Lee
2009-05-16 17:38 ` Rik van Riel
2009-05-17 1:19 ` Wu Fengguang
2009-05-17 1:27 ` Satish Eerpini
2009-05-17 2:08 ` Wu Fengguang
2009-05-17 4:30 ` Satish Eerpini
2009-05-17 4:57 ` Arjan van de Ven
2009-05-17 4:58 ` Wu Fengguang
2009-05-17 6:18 ` Satish Eerpini
2009-05-17 9:30 ` Wu Fengguang
2009-05-17 12:01 ` Satish Eerpini
2009-05-17 12:17 ` Wu Fengguang [this message]
2009-05-17 12:27 ` Satish Eerpini
2009-05-17 12:39 ` Wu Fengguang
2009-05-17 13:03 ` Satish Eerpini
2009-05-17 13:11 ` Wu Fengguang
2009-05-17 13:43 ` Satish Eerpini
2009-05-17 13:14 ` Michael S. Zick
2009-05-16 2:28 ` Satish Eerpini
2009-05-16 14:25 ` Satish Eerpini
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=20090517121711.GA3583@localhost \
--to=fengguang.wu@intel.com \
--cc=cl@linux-foundation.org \
--cc=eerpini@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.org \
--cc=riel@redhat.com \
/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.