From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: `bzr viz' slooow
Date: Wed, 27 Jan 2010 08:02:37 -0500 [thread overview]
Message-ID: <E1Na7XZ-00044V-LH@fencepost.gnu.org> (raw)
In-Reply-To: <87ljfjvike.fsf@telefonica.net> (message from Óscar Fuentes on Wed, 27 Jan 2010 13:27:45 +0100)
> From: Óscar_Fuentes <ofv@wanadoo.es>
> Date: Wed, 27 Jan 2010 13:27:45 +0100
>
> The VC DAG is not a tree.
Nevertheless, I see no reason why tree-widget couldn't support some
reasonable display based on "bzr log".
> Some projects (i.e. Emacs) have a large number of nodes on their DAG (of
> the order of hundreds of thousands.) A C++ extension like qlog, for
> instance, uses 280 MB of RES memory on GNU/Linux x86_64 while displaying
> the Emacs DAG.
According to this:
bzr log --line -n0 | wc
we had 106759 revisions 3 weeks ago (I don't have an up to date tree
where I type this). To use up 280MB for that means 2KB per revision,
which sounds almost unbelievable. Maybe I'm missing something
important.
> It would be great to have that functionality on Emacs. It's VC-log on
> steroids.
Sure. Any volunteers?
prev parent reply other threads:[~2010-01-27 13:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 17:05 `bzr viz' slooow Werner LEMBERG
2010-01-26 17:48 ` Eli Zaretskii
2010-01-26 22:07 ` Werner LEMBERG
2010-01-27 4:11 ` Eli Zaretskii
2010-01-27 6:14 ` Werner LEMBERG
2010-01-27 11:29 ` Eli Zaretskii
2010-01-27 12:01 ` Werner LEMBERG
2010-01-27 13:03 ` Eli Zaretskii
2010-01-26 18:37 ` Óscar Fuentes
2010-01-26 22:16 ` Werner LEMBERG
2010-01-26 23:13 ` Óscar Fuentes
2010-01-27 6:15 ` Werner LEMBERG
2010-01-26 22:59 ` Dan Nicolaescu
2010-01-27 5:22 ` Ken Hori
2010-01-27 6:02 ` Werner LEMBERG
2010-01-27 11:10 ` Óscar Fuentes
2010-01-27 11:30 ` Werner LEMBERG
2010-01-27 11:51 ` Werner LEMBERG
2010-01-27 12:05 ` Eli Zaretskii
2010-01-27 12:27 ` Óscar Fuentes
2010-01-27 13:02 ` Eli Zaretskii [this message]
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=E1Na7XZ-00044V-LH@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).