Git development
 help / color / mirror / Atom feed
From: Marco Costalba <mcostalba@yahoo.it>
To: git@vger.kernel.org
Subject: [ANNOUNCE qgit-0.95]
Date: Sat, 24 Sep 2005 09:06:40 -0700 (PDT)	[thread overview]
Message-ID: <20050924160641.60151.qmail@web26307.mail.ukl.yahoo.com> (raw)

This is a performance update release.

The detailed list of changes is below, but the bottom line is 
qgit-0.95 is _really_ fast.

It tooks about 4 seconds, on my box, to run qgit --all on today linux tree against 
about 65 seconds with gitk. Also the used memory it seems lower.

As a 'theoretical maximum speed' a bare:

git-rev-list --header --topo-order --parents HEAD > /dev/null

Runs in about 2 seconds.

So this is the main reason I post this release. I doubt a little bit about this results 
because the spread with gitk it seems too much, so I would like a double check.

NOTE: Before to test qgit you need to UNSET flag 

           edit->settings->cache->'diff against working dir'

to avoid a slow 'git-status' (with involved 'git-update-index --refresh') call.


CHANGELOG

- more scalable pixmap memory handling.
  Graph pixmaps are created only for visible items and freed
  when log lines became not visible so that the amount of memory
  used is constant and independent from archive size. This is also a
  performance improvement because of the 'lazy setup' policy.

- changed GUI update policy to group all the updates in one big chunk at
  fixed intervals. This is faster then an incremental update.

- more scalable file names handling.
  File paths are splitted in base and file name, both are then indipendently
  indexed. This gives huge memory savings and also better scalability because the
  'different file names' set grows much more slowly then new commits. Using two index 
  tables gives good memory saving when you have lot of files in the same (deep) directory.

- Rewritten git-rev-list parsing to avoid as much as possible to move data around.


INSTALLATION

You need scons and Qt developer libs version 3.3.4 or better already installed. You need 'mt'
version of Qt libraries.

QGit is NOT compatible with Qt4.

On some platforms (Debian) you should set QTDIR before to compile.


DOWNLOAD

Download link is:
http://prdownloads.sourceforge.net/qgit/qgit-0.95.tar.bz2?download

But now there is also a git archive: 
http://digilander.libero.it/mcostalba/qgit.git

Please use 'cg-clone http://digilander.libero.it/mcostalba/qgit.git' 
I still have to set-up a 'git clone' friendly archive.

If you have problems with the sources you can download a binary:
http://digilander.libero.it/mcostalba/qgit



Marco



		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

             reply	other threads:[~2005-09-24 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 16:06 Marco Costalba [this message]
2005-09-24 18:16 ` [ANNOUNCE qgit-0.95] Petr Baudis
2005-09-25  6:32 ` Alan Chandler
2005-09-25  6:47   ` Alan Chandler
  -- strict thread matches above, loose matches on Subject: below --
2005-09-25  5:52 Marco Costalba
2005-09-25 19:19 ` Josef Weidendorfer
2005-09-25  7:07 Marco Costalba
2005-09-25 18:56 ` Josef Weidendorfer
2005-09-25 20:46   ` Robin Farine
2005-09-25 20:37 Marco Costalba
2005-09-25 21:57 Marco Costalba

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=20050924160641.60151.qmail@web26307.mail.ukl.yahoo.com \
    --to=mcostalba@yahoo.it \
    --cc=git@vger.kernel.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