From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: esr@thyrsus.com
Cc: Nicholas Krause <xerofoify@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
law@redhat.com, gcc@gcc.gnu.org
Subject: Re: Commit messages and the move to git
Date: Tue, 19 Nov 2019 19:49:00 -0000 [thread overview]
Message-ID: <15a68e1b-90cf-9720-6122-8ad257e34243@arm.com> (raw)
In-Reply-To: <0503263a-2384-c738-213d-5a877f79a352@arm.com>
On 19/11/2019 19:47, Richard Earnshaw (lists) wrote:
> On 19/11/2019 19:32, Eric S. Raymond wrote:
>> Richard Earnshaw (lists) <Richard.Earnshaw@arm.com>:
>>> I was looking at the reposurgeon code last night, and I think I can see what
>>> the problem *might* be, but I haven't had time to produce a testcase.
>>>
>>> Some of our commits have mergeinfo that looks a bit like this:
>>>
>>> 202022-202023,202026,202028-202029,202036,202039-202041,202043-202044,202048-202049,202051-202056,202058-202061,202064-202065,202068-202071,202077,202079-202082,202084,202086-202088,202092-202104,202106-202113,202115-202119,202121,202124-202134,202139,202142-202146,202148-202150,202153-202154,202158-202159,202163-202165,202168,202172,202174,202179-202180,202184-202192,202195,202197,202202-202208,202225-202230,202232-202233,202237-202239,202242,202244-202245,202247,202250-202251,202258-202264,202266,202269,202271-202275,202279,202281-202282,202284,202286,202289-202292,202296-202299,202301-202302,202305,202309,202311-202323,202327-202335,202337,202339,202343-202346,202350,202352,202356-202357,202359-202360,202363-202371,202373-202374,202377,202379-202382,202384,202389,202391-202395,202398-202407,202409,202411,202416-202418,202421
>>>
>>> which is a massive long list with a number of holes in it.
>>>
>>> But I suspect the holes are really commits to other branches and that in the
>>> above describes a linear chain along one branch. If so, rather than
>>> producing links to each subgroup (and perhaps dropping single non-list
>>> elements, the description can be mapped back to a contiguous sequence of
>>> commits down a branch and thus should really resolve to a single child being
>>> used for the merge source. At present, I think for the above we're seeing a
>>> child reference created for each subrange in that list.
>>
>> I have no doubt you are correct. Detecting such interrupted ranges ia
>> foing to be... interesting.
>>
>>> Incidentally, the mergeinfo pass on the gcc repo is currently taking about 8
>>> hours on my machine, that's 80-90% of the entire conversion time. But it
>>> might be related to the above.
>>
>> You must be running the old Python code, there was on O(n**2) in that
>> phase that has since been fixed. Try the Go code from
>> https://gitlab.com/esr/reposurgeon; it is *much* faster.
>>
>
> Nope, that was from running the go version from yesterday. This one, to
> be precise: 1ab3c514c6cd5e1a5d6b68a8224df299751ca637
>
> This pass used to be very fast a couple of weeks back, but something
> went in recently that's caused a major slowdown.
>
> Oh, and I've been having problems with the ChangeLogs command as well.
> It used to run fine on my machine (128G), but now it's started blowing
> memory and taking my X server down.
>
> R.
>
> R.
>
Here's the stats output:
# Statistics on read and processing times
timing
commits: 276738 (from 278380)
parsing: 2.85% 14m22.861991058s
cleaning: 0.32% 1m37.653100823s
filemaps: 0.37% 1m52.851558995s
commits: 4.40% 22m15.380157228s
rootcommit: 0.00% 8.779µs
branches: 0.04% 12.710113776s
parents: 0.00% 121.73484ms
root: 0.00% 267.997µs
branchlinks: 0.00% 10.58361ms
mergeinfo: 91.67% 7h43m15.416510183s
branches: 0.00% 11.616µs
dejunk: 0.04% 10.672889443s
polishing: 0.04% 11.249533399s
tagifying: 0.03% 10.528735532s
tagcleaning: 0.03% 9.880052536s
debubbling: 0.00% 1.384357053s
renumbering: 0.20% 59.718288526s
total: 9/sec 8h25m20.439895394s
next prev parent reply other threads:[~2019-11-19 19:49 UTC|newest]
Thread overview: 139+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 10:29 Richard Earnshaw (lists)
2019-11-04 12:11 ` Arnaud Charlet
2019-11-04 12:43 ` Martin Jambor
2019-11-04 17:43 ` Segher Boessenkool
2019-11-04 16:04 ` Jeff Law
2019-11-04 16:18 ` Richard Earnshaw (lists)
2019-11-05 15:48 ` Richard Earnshaw
2019-11-07 14:27 ` Eric S. Raymond
2019-11-08 13:43 ` Richard Earnshaw (lists)
2019-11-09 6:01 ` Eric S. Raymond
2019-11-18 15:32 ` Richard Earnshaw (lists)
2019-11-18 15:55 ` Segher Boessenkool
2019-11-18 16:48 ` Richard Earnshaw (lists)
2019-11-18 17:11 ` Segher Boessenkool
[not found] ` <8c32c288-e9e6-b01b-7911-3f186116da85@gmail.com>
2019-11-18 17:24 ` Nicholas Krause
2019-11-18 17:26 ` Nicholas Krause
2019-11-18 17:46 ` Richard Earnshaw (lists)
2019-11-18 17:49 ` Richard Earnshaw (lists)
2019-11-18 17:55 ` Nicholas Krause
2019-11-18 18:05 ` Richard Earnshaw (lists)
2019-11-18 18:24 ` Joseph Myers
2019-11-19 11:26 ` Eric S. Raymond
2019-11-19 11:25 ` Eric S. Raymond
2019-11-19 11:46 ` Richard Earnshaw (lists)
2019-11-19 19:32 ` Eric S. Raymond
2019-11-19 19:47 ` Richard Earnshaw (lists)
2019-11-19 19:49 ` Richard Earnshaw (lists) [this message]
2019-11-19 22:14 ` Eric S. Raymond
2019-11-19 22:19 ` Richard Earnshaw (lists)
2019-11-21 16:41 ` Joseph Myers
2019-11-21 16:52 ` Richard Earnshaw (lists)
2019-11-21 18:11 ` Eric S. Raymond
2019-11-21 18:09 ` Eric S. Raymond
2019-11-21 19:22 ` Richard Earnshaw (lists)
2019-11-19 19:43 ` Richard Earnshaw (lists)
2019-11-19 22:08 ` Eric S. Raymond
2019-11-18 17:38 ` Richard Earnshaw (lists)
2019-11-18 18:53 ` Segher Boessenkool
2019-11-18 19:14 ` Richard Earnshaw (lists)
2019-11-18 19:21 ` Richard Earnshaw (lists)
2019-11-18 19:44 ` Segher Boessenkool
2019-11-18 20:53 ` Jason Merrill
2019-11-18 21:38 ` Richard Earnshaw (lists)
2019-11-19 14:57 ` Jason Merrill
2019-11-19 16:31 ` Segher Boessenkool
2019-11-19 16:47 ` Jonathan Wakely
2019-11-19 16:48 ` Jason Merrill
2019-11-19 19:36 ` Eric S. Raymond
2019-11-19 23:29 ` Segher Boessenkool
2019-11-19 23:44 ` Joseph Myers
2019-11-19 23:51 ` Nicholas Krause
2019-11-20 8:55 ` Jonathan Wakely
2019-11-20 14:50 ` Szabolcs Nagy
2019-11-20 17:30 ` Richard Earnshaw (lists)
2019-11-20 8:58 ` Jonathan Wakely
2019-11-20 11:27 ` Segher Boessenkool
2019-11-20 11:30 ` Richard Earnshaw (lists)
2019-11-20 11:42 ` Segher Boessenkool
2019-11-20 14:25 ` Jason Merrill
2019-11-20 16:01 ` Segher Boessenkool
2019-11-19 16:49 ` Richard Earnshaw (lists)
2019-12-02 10:54 ` Richard Earnshaw (lists)
2019-12-02 15:35 ` Segher Boessenkool
2019-12-02 16:19 ` Richard Earnshaw (lists)
2019-12-02 17:25 ` Segher Boessenkool
2019-12-02 17:47 ` Richard Earnshaw (lists)
2019-12-02 18:00 ` Segher Boessenkool
2019-12-02 18:11 ` Richard Earnshaw (lists)
2019-12-02 18:17 ` Eric S. Raymond
2019-12-02 20:24 ` Joseph Myers
2019-12-03 0:48 ` Segher Boessenkool
2019-12-03 9:44 ` Richard Earnshaw (lists)
2019-12-03 10:12 ` Richard Earnshaw (lists)
2019-12-02 20:22 ` Richard Sandiford
2019-12-04 23:52 ` Richard Earnshaw (lists)
2019-12-05 10:26 ` Jonathan Wakely
2019-12-05 10:32 ` Jonathan Wakely
2019-12-05 10:36 ` Richard Earnshaw (lists)
2019-12-05 10:41 ` Jonathan Wakely
2019-12-05 10:54 ` Jonathan Wakely
2019-12-05 13:18 ` Joseph Myers
2019-12-05 17:10 ` Eric S. Raymond
2019-12-05 17:22 ` Joseph Myers
2019-12-05 17:45 ` Eric S. Raymond
2019-12-05 20:14 ` Joseph Myers
2019-12-05 20:46 ` Joseph Myers
2019-12-05 21:14 ` Eric S. Raymond
2019-12-05 21:13 ` Eric S. Raymond
2019-12-05 15:33 ` Eric S. Raymond
2019-12-18 23:43 ` Joseph Myers
2019-12-19 0:01 ` Joseph Myers
2019-12-19 9:27 ` Jonathan Wakely
2019-12-19 11:05 ` Jonathan Wakely
2019-12-19 11:50 ` Richard Earnshaw (lists)
2019-12-19 11:58 ` Richard Earnshaw (lists)
2019-12-19 12:23 ` Jonathan Wakely
2019-12-19 12:33 ` Richard Earnshaw (lists)
2019-12-19 12:35 ` Jonathan Wakely
2019-12-19 12:42 ` Richard Earnshaw (lists)
2019-12-19 13:34 ` Jonathan Wakely
2019-12-19 16:00 ` Joseph Myers
2019-12-19 16:06 ` Richard Earnshaw (lists)
2019-12-19 14:29 ` Joseph Myers
2019-12-19 15:17 ` Jonathan Wakely
2019-12-19 15:20 ` Richard Earnshaw (lists)
2019-12-19 15:44 ` Jonathan Wakely
2019-12-19 15:47 ` Joseph Myers
2019-12-19 15:48 ` Jonathan Wakely
2019-12-19 15:48 ` Richard Earnshaw (lists)
2019-12-19 15:49 ` Joseph Myers
2019-12-19 16:27 ` Jonathan Wakely
2019-12-19 16:28 ` Jonathan Wakely
2019-12-19 16:33 ` Joseph Myers
2019-12-19 16:39 ` Jonathan Wakely
2019-12-19 16:43 ` Joseph Myers
2019-12-20 20:30 ` Joseph Myers
2019-12-20 21:30 ` Jonathan Wakely
2019-12-20 21:41 ` Joseph Myers
2019-12-20 22:11 ` Jonathan Wakely
2019-12-20 22:58 ` Joseph Myers
2019-12-20 23:23 ` Jonathan Wakely
2019-12-20 23:53 ` Joseph Myers
2019-12-19 11:16 ` Jakub Jelinek
2019-12-19 15:05 ` Richard Earnshaw (lists)
2019-11-04 16:19 ` Jonathan Wakely
2019-11-04 16:35 ` Richard Earnshaw (lists)
2019-11-04 17:33 ` Segher Boessenkool
2019-11-04 17:42 ` Joseph Myers
2019-11-04 17:50 ` Segher Boessenkool
2019-11-05 11:07 ` Jonathan Wakely
2019-11-05 11:28 ` Jason Merrill
2019-11-05 14:12 ` Marek Polacek
2019-11-05 21:40 ` Richard Earnshaw (lists)
2019-11-05 14:50 ` David Malcolm
2019-11-05 22:08 ` Segher Boessenkool
2019-11-05 20:16 ` Segher Boessenkool
2019-11-05 21:01 ` Iain Sandoe
2019-11-05 2:51 ` Kewen.Lin
2019-11-05 21:42 ` Richard Earnshaw (lists)
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=15a68e1b-90cf-9720-6122-8ad257e34243@arm.com \
--to=richard.earnshaw@arm.com \
--cc=esr@thyrsus.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=xerofoify@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).