Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Git Clone speed: ssh vs http

My stash admins have installed a version of stash that supports ssh, so I consider using ssh for clone/push/pull/... instead of http -- for development, not just CI.

Using SourceTree (v1.8.1, if it matters) on OSX Mavericks, which protocol should be faster -- http or ssh? Initial clone is relatively rare, so the main factor is the speed of pull/fetch/checkout and push.

1 answer

1 accepted

1 vote
Answer accepted

Hi Noam,

It's unlikely that there is a significant speed difference between SSH and HTTPS. Both transports send the same data over the wire and perform SSL encryption. Depending on how Stash has been set up, the SSL encryption for HTTPS could be performed by a reverse proxy (Apache/Nginx) which would reduce the load on the Stash server and could translate is slightly better performance over HTTPS than you'd get over SSH, but it's hard to say.

If you're feeling like experimenting, you can set up two remotes for your repository and see which one works best for you.

Hope that helps,


Actually, since this in inside the intranet, they use plain http. I suppose it means that in this setup http is likely to be faster.

We are seeing an extremely significant different with ssh vs https.


Today we are getting about 15 MiB/s over https and only 1 MiB/s over ssh from the same machine , same repository.


Our https/ SSL is configured in a reverse proxy , we are using an f5 appliance.


We would like to speed up our ssh performance.

Like # people like this

SSL Overhead is negligible now a days with added security and privacy concerns going other way around is not a good option anyway!  

If you are getting very low speed on SSL make sure receiving PC/Device is capable of handling those speeds. Run a speed test via HTTP  & HTTPS and compare yourself. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

244 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you