From: Michael Powe <michael+gnus@trollope.org>
Subject: Re: 1st character change in file takes forever
Date: Sun, 22 Dec 2002 19:15:21 GMT [thread overview]
Message-ID: <uisxlc1ba.fsf@trollope.org> (raw)
In-Reply-To: m0of7e70g4.fsf@bloombergREMOVETHISPART.com
>>>>> "David" == David Klein <dklein@bloombergREMOVETHISPART.com> writes:
David> Barry Margolin <barmar@genuity.net> writes:
>> In article <m08yyodagg.fsf@bloombergREMOVETHISPART.com>, David
>> Klein <dklein@bloombergREMOVETHISPART.com> wrote: >When I first
>> try to insert a character into a buffer that is >associated
>> with a file on disk, the insert takes close to a minute!
>> During that first change, Emacs checks whether someone else has
>> modified the file, and also checks for a lock file. For some
>> reason, these checks are taking a long time. Try doing a
>> system call trace to see what it's doing during that time.
David> Assuming by "a system call trace" you meant the strace
David> function, I did the following:
>> emacs junk1& strace -c -f -ff -o emacs_trace -q -r -t -T -p1238
David> (1238 was the pid of emacs. After running the strace
David> command, I pressed the spacebar once in emacs. When it
David> finally inserted the space into the buffer, I ^C'ed the
David> strace).
>> cat emacs_trace
[ ... ]
David> I have no idea how to continue, besides the fact that
David> 255963 read syscalls seems slightly on the high side for
David> inserting a single character. Any ideas how to continue?
are you on a network? if so, does this behavior continue if you
disconnect the machine from the network?
mp
--
Michael Powe Waterbury, CT
-------------------------------------------------------------
"The most likely way for the world to be destroyed, most experts
agree, is by accident. That's where we come in. We're computer
professionals. We cause accidents." -- Nathaniel Borenstein
next prev parent reply other threads:[~2002-12-22 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 13:46 1st character change in file takes forever David Klein
2002-12-17 15:30 ` Barry Margolin
2002-12-22 11:33 ` David Klein
2002-12-22 19:15 ` Michael Powe [this message]
2002-12-24 8:19 ` David Klein
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uisxlc1ba.fsf@trollope.org \
--to=michael+gnus@trollope.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).