9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Software preservation in the post-hg era
Date: Sun, 10 May 2020 06:51:09 +0200	[thread overview]
Message-ID: <CAK8RtFrPJ4B0SqD_aC2zHQYL4ki2ednwWtqbpv6V03FRSmLmiQ@mail.gmail.com> (raw)
In-Reply-To: <CAG2UyHpY1djXz2aJdw_wnPdC_h1pZyjHK8uyQC2upwODHjDECw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]

Den tors 7 maj 2020 16:17Dave MacFarlane <driusan@gmail.com> skrev:

>
> On Mon, Mar 30, 2020 at 9:12 PM Sean Hinchee <henesy.dev@gmail.com> wrote:
>
>> As a footnote, there's a decent git client written in Go that works
>> alright on plan9 [4], but it's slow and memory intensive at the
>> moment.
>>
>>
> [...]
>
> [4] https://github.com/driusan/dgit
>>
>
> This (and the fact that the speed of Go on Plan9/amd64 seems to be finally
> be useable enough to do development again as of 1.14..) finally gave me the
> kick I needed to fix some of the hacks that were causing performance
> problems on clone. The self-clone time went from ~160s to ~13s on my
> machine (compared to ~8s with "real" git) If there's other parts that you
> were referring to as being slow and memory intensive let me know (or if you
> still find it's memory intensive, I didn't benchmark that part..)
>
> - Dave
>


How does it compare performance wise with git9 ?

https://github.com/oridb/git9


*9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/T303744e1ec6d2108-Mbc073232aabcf555586a9843>
>

[-- Attachment #2: Type: text/html, Size: 3069 bytes --]

  parent reply	other threads:[~2020-05-10  4:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  1:11 Sean Hinchee
2020-03-31  1:52 ` Fazlul Shahriar
2020-03-31 14:45 ` ori
2020-03-31 16:59   ` Lucio De Re
2020-03-31 18:37   ` Dave MacFarlane
2020-03-31 19:08     ` Sigrid Solveig Haflínudóttir
2020-04-01 10:47     ` Charles Forsyth
2020-03-31 18:39 ` Xiao-Yong Jin
2020-04-01  1:00 ` Fazlul Shahriar
2020-05-07 14:15 ` Dave MacFarlane
2020-05-10  4:25   ` Lucio De Re
2020-05-10 16:27     ` hiro
2020-05-10  4:51   ` Jens Staal [this message]
2020-05-10 19:04     ` ori
2020-05-10 19:13     ` Dave MacFarlane
2020-05-10 18:37 ` Jim Manley

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=CAK8RtFrPJ4B0SqD_aC2zHQYL4ki2ednwWtqbpv6V03FRSmLmiQ@mail.gmail.com \
    --to=staal1978@gmail.com \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).