all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How expansive "bzr update" for Emacs trunk?
Date: Sun, 01 Aug 2010 14:10:48 +0300	[thread overview]
Message-ID: <i33kno$8lt$1@dough.gmane.org> (raw)
In-Reply-To: <4C547772.4040908@easy-emacs.de>

On 2010-07-31 22:20, Andreas Röhler wrote:
> Am 31.07.2010 19:04, schrieb Oleksandr Gavenko:
>> On 2010-07-27 11:13, Tassilo Horn wrote:
>>> Oleksandr Gavenko<gavenkoa@gmail.com> writes:
>>>
>>> Hi Oleksandr,
>>>
>>>> I mark that "bzr update" take about 1 MiB for
>>>> "Finding Revisions" and a lot MiB
>>>> (5.5 MiB between yesterday and today).
>>>>
>>>> Is really bzr so dumb that require a lot of network traffic?
>>>
>>> Yes, accessing a bzr repository via http produces extremely much network
>>> traffic.
>>>
>>>> I restricted with 3G or GPRS Internet connection.
>>>> One time a month commit I get about 5 hours
>>>> (~7 KiB/sec download speed)!
>>>
>>> Oh, that must be really awful.
>>>
>>>> So may be good switch to ssh protocol and set compression?
>>>
>>> Yes, it's planned to switch the Emacs repository to a smart server using
>>> ssh access. See the following tickets on savannah and the discussion:
>>>
>>> https://savannah.gnu.org/support/?107077
>>> https://savannah.gnu.org/support/index.php?107143
>>> http://lists.gnu.org/archive/html/savannah-hackers-public/2010-03/msg00011.html
>>>
>>>
>>>
>>> But the latest traffic seems to be in March, so I have no clue about the
>>> current status...
>>
>> Thanks for replay. A read tickets.
>>
>> This ticket valuable for developer.
>>
>> I need only read access
>
>
> In this case you may try
>
> git clone git://repo.or.cz/emacs.git
>
> an emacs-clone at a git-repo, updated quite often.
>
> Should be faster.

Thanks. I try use git mirror. Also I found wiki link:

http://www.emacswiki.org/emacs/EmacsFromGit

There are two other mirror links.

Interesting that wiki state that git mirror occupy ~300 MiB.
My local bzr 2.0 repo occupy:

   $ du -s -m emacs/.bzr
260	emacs/.bzr
   $ du -s -m emacs/trunk/.bzr
1	emacs/trunk/.bzr

So we may be think that bzr storage more efficient.

But also I sadly notice that such simple operation as
getting log or annotate for trunk files take about 15-20 seconds!

May be because large history.

My experience with Mercurial and
server side SVN with up to 30.000 commits take
less then 1-2 sec. for this operations.

-- 
Best regards!




  reply	other threads:[~2010-08-01 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 20:39 How expansive "bzr update" for Emacs trunk? Oleksandr Gavenko
2010-07-27  8:13 ` Tassilo Horn
2010-07-31 17:04   ` Oleksandr Gavenko
2010-07-31 19:20     ` Andreas Röhler
2010-08-01 11:10       ` Oleksandr Gavenko [this message]
2010-08-01 17:53         ` Andreas Röhler
2010-08-01  9:58     ` Tassilo Horn
     [not found] <mailman.20.1280176760.16726.help-gnu-emacs@gnu.org>
2010-07-27 17:11 ` Jason Earl

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='i33kno$8lt$1@dough.gmane.org' \
    --to=gavenkoa@gmail.com \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.