git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tamas Csabina <tcsabina@gmail.com>
To: git@vger.kernel.org
Subject: slow process of post-receive script on a remote (samba) share
Date: Thu, 13 Jun 2013 11:18:32 +0200	[thread overview]
Message-ID: <CAH+Cn14TLpR1KT+3GND2Zmb8tDmFBP7AWpyrT7nVeMFw6V7FGA@mail.gmail.com> (raw)

Dear list,

I am using Git bash from version 1.8.3.msysgit.0, on a Windows 7x64 PC.
I have an issue with executing git push if I have a post-receive
script configured.
The content of the script is not really important, as if I have a
script that contains only commented out lines (around 70 lines), my
git push command is delayed with around 5 seconds.


I`ve tested the script on another PC and it is working fine. No delay
at all. So there are some issues on my PC regarding how git processes
remote scripts.

I took a wireshark trace with 2 scenarios on my PC:

 1. just execute `cat <path_to_the_script>\post-receive` command in the git bash
 2. did a `real` git push

Results of the wireshark traces shows:

 1. Read AndX Request, FID: 0x228f, 1024 bytes at offset 0 (1024 bytes
at time, always)
 2. Read AndX Request, FID: 0x21c9, 1 byte at offset 0 (1 byte, always)

Conclusion:
git push command reads the post-receive script in 1 byte chunks, which
dramatically slows down the execution process.


If more information is required about my setup or configuration, I
will provided it happily, but I think this 1 byte read is the main
reason for the issue.

Has anyone seen something similar? Or have any clues what is going on?


Thanks,
tamas

ps: this is my 3rd (or 4th) attempt to post on the mailing list, using
a different email account this time. If any of the previous attempt
also arrived, then sorry for the double posts.

             reply	other threads:[~2013-06-13  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  9:18 Tamas Csabina [this message]
2013-06-13 12:19 ` slow process of post-receive script on a remote (samba) share Thomas Rast
2013-06-13 13:47   ` Tamas Csabina
2013-06-13 14:29     ` Thomas Rast
2013-06-14 13:06       ` Tamas Csabina

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=CAH+Cn14TLpR1KT+3GND2Zmb8tDmFBP7AWpyrT7nVeMFw6V7FGA@mail.gmail.com \
    --to=tcsabina@gmail.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).