From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: patch for documentation about version control
Date: 11 Nov 2004 11:06:33 -0500 [thread overview]
Message-ID: <jk8y98fjzq.fsf@glug.org> (raw)
In-Reply-To: Andre Spiegel's message of "Thu, 11 Nov 2004 12:55:17 +0100"
Andre Spiegel <spiegel@gnu.org> writes:
What about the efficiency of your parser, though? How long does it
take to construct this full parse tree for a large RCS master with
many revisions?
i haven't done any serious performance testing. looking around locally,
the biggest file i could find was a ChangeLog of size 223492 bytes w/
252 revisions. this is probably not representative since the typical
revision in such a file is to add some text at the top, very simple as
far as edits go...
anyway, on a 300MHz openbrick, w/ the modified vc-rcs.elc loaded,
(let ((start (current-time)))
(call-interactively 'vc-annotate)
(time-subtract (current-time) start))
=> (0 11)
other files i've tested to date have less revisions and are much faster,
no surprise. probably a big win would be to avoid `with-temp-buffer'
when parsing the rev bodies, keeping all scanning in the current buffer
and consing a string only at the end.
thi
next prev parent reply other threads:[~2004-11-11 16:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 6:55 patch for documentation about version control Alex Ott
2004-11-09 9:13 ` Andre Spiegel
2004-11-12 9:11 ` Alex Ott
2004-11-09 18:21 ` Karl Fogel
2004-11-09 21:32 ` Stefan Monnier
2004-11-09 21:34 ` Stefan Monnier
2004-11-09 22:09 ` David Kastrup
2004-11-10 9:00 ` Thien-Thi Nguyen
2004-11-10 9:22 ` Andre Spiegel
2004-11-10 16:43 ` Thien-Thi Nguyen
2004-11-11 11:55 ` Andre Spiegel
2004-11-11 15:11 ` Stefan
2004-11-11 15:36 ` Andre Spiegel
2004-11-11 15:25 ` Thien-Thi Nguyen
2004-11-11 16:06 ` Thien-Thi Nguyen [this message]
2004-11-11 18:25 ` Thien-Thi Nguyen
2004-11-11 20:59 ` Andre Spiegel
2004-11-12 9:33 ` Thien-Thi Nguyen
2004-11-10 9:30 ` Andre Spiegel
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=jk8y98fjzq.fsf@glug.org \
--to=ttn@glug.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).