Poor git clone performance since 5 Dec (Thursday)

[genisd]

Select Topic Area

Bug

Body

Dear community,

we're seeing abysmally slow git clone performance since 5 December.
We are running our own github action runners inside the google cloud using the awesome actions runner controller.

However since 5 december our git clone operation which used to go at up to 50 MB/s is now always < 1 MB/s often under 200 kb/s and then subsequently fails for our monorepo's.

Anyone else having this issue?

We're running our actions workers in the google cloud inside europe-west4.

Example:

  Receiving objects:  64% (3106/4781), 9.16 MiB | 168.00 KiB/s
  Receiving objects:  64% (3106/4781), 9.34 MiB | 175.00 KiB/s
  Receiving objects:  64% (3106/4781), 9.51 MiB | 179.00 KiB/s
  Receiving objects:  64% (3106/4781), 9.71 MiB | 176.00 KiB/s
  Receiving objects:  64% (3106/4781), 9.93 MiB | 183.00 KiB/s
  Receiving objects:  64% (3106/4781), 10.11 MiB | 182.00 KiB/s
  Receiving objects:  64% (3106/4781), 10.31 MiB | 186.00 KiB/s
  Receiving objects:  64% (3106/4781), 10.51 MiB | 207.00 KiB/s
  Receiving objects:  64% (3106/4781), 10.74 MiB | 202.00 KiB/s
  Receiving objects:  64% (3106/4781), 10.86 MiB | 204.00 KiB/s
  Error: error: 5527 bytes of body are still expected
  fetch-pack: unexpected disconnect while reading sideband packet
  Error: fatal: early EOF
  Error: fatal: fetch-pack: invalid index-pack output
  Error: The process '/usr/bin/git' failed with exit code 128

actions/checkout@v4
  with:
    ref: 5ee869d6461faecd3cf505238787ec1d3c33a023
    repository: org/exampleRepository
    token: ***
    ssh-strict: true
    persist-credentials: true
    clean: true
    sparse-checkout-cone-mode: true
    fetch-depth: 1
    fetch-tags: false
    lfs: false
    submodules: false
    set-safe-directory: true

This is a small repo which fails to clone more often than not 😢

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[genisd]

We've switched our workflows to ssh clone, but would much rather prefer to throwaway that code/complexity and get the old behaviour back. The above clone goes through git but with github https clone.

The amount of times we're seeing exactly 1 MB/s and a division of that makes us think it's a bandwidth throttle on a per source IP basis.
I hope this change can be rolled back/reverted. I spent my entire day reworking all our CI/CD flows to work around this, but the complexity has grown which is unfortunate.