From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Iucha, Florin" <Florin.Iucha@amd.com>
Cc: Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: High locking contention during repack?
Date: Wed, 12 Dec 2018 17:54:07 +0100 [thread overview]
Message-ID: <CACBZZX6YsWs7Q3g3UARgBLQZniZUuPPuM2kaw-PHmtO+ZZrnkQ@mail.gmail.com> (raw)
In-Reply-To: <SN1PR12MB23849A5B991FB7D9213FB64595A70@SN1PR12MB2384.namprd12.prod.outlook.com>
On Wed, Dec 12, 2018 at 5:52 PM Iucha, Florin <Florin.Iucha@amd.com> wrote:
>
> Jeff,
>
> Thank you for the advice, I will reduce the depth.
>
> Running "git pack-objects --all --no-reuse-delta --delta-base-offset --stdout </dev/null >/dev/null", it got to 99% fairly quickly, now it has 5 threads running (using 99.9% CPU), but the "dstat 5" still shows lots of nothing, with some heavy system activity:
>
> --total-cpu-usage-- -dsk/total- -net/total- ---paging-- ---system--
> usr sys idl wai stl| read writ| recv send| in out | int csw
> 1 8 91 0 0| 166k 224k| 0 0 | 0 0 |6892 970
> 0 13 87 0 0| 0 0 | 333B 1758B| 0 0 |2285 1374
> 0 13 87 0 0| 0 0 | 309B 1190B| 0 0 |2233 1265
> 0 13 87 0 0| 0 0 | 282B 1053B| 0 0 |2174 1239
> 0 13 87 0 0| 0 0 | 278B 1251B| 0 0 |1930 1173
> 0 13 87 0 0| 0 0 | 274B 942B| 0 0 |1987 1139
> 0 13 87 0 0| 0 0 | 264B 1168B| 0 0 |1928 1205
> 0 13 87 0 0| 0 0 | 388B 2435B| 0 0 |2245 1280
> 0 13 87 0 0| 0 0 | 268B 1145B| 0 0 |2225 1221
> 0 13 87 0 0| 0 0 | 164B 732B| 0 0 |2607 1333
> 0 13 87 0 0| 0 0 | 156B 996B| 0 0 |2100 1270
> 0 13 87 0 0| 0 0 | 206B 1019B| 0 0 |2192 1296
> 0 13 87 0 0| 0 0 | 198B 824B| 0 0 |2019 1236
> 0 13 87 0 0| 0 0 | 245B 435B| 0 0 |1974 1195
> 0 13 87 0 0| 0 0 | 252B 855B| 0 0 |1852 1166
> 0 13 87 0 0| 0 0 | 230B 758B| 0 0 |2066 1299
> 0 13 87 0 0| 0 0 | 284B 925B| 0 0 |1860 1225
> 0 13 87 0 0| 0 0 | 289B 2682B| 0 0 |1796 1197
> 0 13 87 0 0| 0 0 | 939B 1263B| 0 0 |1913 1304
> 0 13 87 0 0| 0 0 |1212B 1366B| 0 0 |1915 1343
>
> I will try running the command under the debugger and stop it when it gets to this point and poke around.
FWIW compiling with gcc's gprof support is probably a better way to
figure out "what was my program doing all this time?".
next prev parent reply other threads:[~2018-12-12 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 3:01 High locking contention during repack? Iucha, Florin
2018-12-12 11:24 ` Jeff King
2018-12-12 14:04 ` Ævar Arnfjörð Bjarmason
2018-12-12 16:49 ` Iucha, Florin
2018-12-12 16:54 ` Ævar Arnfjörð Bjarmason [this message]
2018-12-12 18:08 ` Iucha, Florin
2018-12-12 18:30 ` Iucha, Florin
2018-12-12 19:05 ` Iucha, Florin
2018-12-12 21:50 ` Iucha, Florin
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACBZZX6YsWs7Q3g3UARgBLQZniZUuPPuM2kaw-PHmtO+ZZrnkQ@mail.gmail.com \
--to=avarab@gmail.com \
--cc=Florin.Iucha@amd.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).