From: <rsbecker@nexbridge.com>
To: "'Arpit Gupta'" <argupta@axway.com>, <git@vger.kernel.org>
Subject: RE: Issue : Writing commits into the git repository takes longer than expected
Date: Mon, 10 Jun 2024 08:58:41 -0400 [thread overview]
Message-ID: <0e4b01dabb35$eee8b5a0$ccba20e0$@nexbridge.com> (raw)
In-Reply-To: <DB9P190MB1500D7DE16D758B8710BEFC7A7C62@DB9P190MB1500.EURP190.PROD.OUTLOOK.COM>
On Monday, June 10, 2024 6:17 AM, Arpit Gupta wrote:
>We are maintaining the different versions of data in git repository using
jgit maven
>library. So, a commit is done on the repository containing properties such
as author
>name, date and time, action, and the file path.
>The file path refers the xml file which contains the action performed and
is stored
>inside the repository.
>
>We have a job running every 5 minutes that commits the information onto the
>repository and the XML file content is over-written every time. Usually,
the commits
>and writing of XML file takes around 4-5 seconds but sometimes the time
while
>committing as well as writing the data increases which also increase the
overall CPU
>utilization of the machine. This behavior is inconsistent with respect to
the process
>and occurs randomly but during this behavior, there is a time when the CPU
>utilization becomes high that all other running processes hangs up which
demands
>the restart of the server.
>
>Could you please suggest which areas should we look for while identifying
the cause
>of this issue? Also, does frequent commit of the content onto repository
can trigger
>this issue?
>In your view, what might be the trigger of this issue and how we can
proceed to
>resolve it?
Are your XML files single line file or is each tag on its own line? Changes
to single-line XML files can cause complete rewrites. If the file is large
enough, this can cause performance issues.
Do you have virus scans running on your repository? These can also cause
issues. Some scanners are more friendly to developers than others. Also, is
this an NFS drive? Is Git LFS involved?
If you have two commits to the same repo happening at once, this can also
cause one commit to be delayed waiting on the lock file. More info is needed
to comment further.
--Randall
next prev parent reply other threads:[~2024-06-10 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 10:17 Issue : Writing commits into the git repository takes longer than expected Arpit Gupta
2024-06-10 12:58 ` rsbecker [this message]
2024-06-12 11:45 ` Arpit Gupta
2024-06-24 5:46 ` Arpit Gupta
-- strict thread matches above, loose matches on Subject: below --
2024-07-12 4:10 Arpit Gupta
2024-07-12 11:35 ` rsbecker
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='0e4b01dabb35$eee8b5a0$ccba20e0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=argupta@axway.com \
--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;
as well as URLs for NNTP newsgroup(s).