Too bad it doesn't work on Cygwin. (I share my ssh config between Linux and Windows.) Too bad ssh doesn't have conditional configuration. (Yes, I know I could script this, but it's a little more pain than I want for this gain.)
Speed Up Git Pull
21–30 of 50 posts
Re: Speed Up Git Pull
#22Dear GitHub,
Please setup local ssh termination to your network.
Thanks,
Alex
Re: Speed Up Git Pull
#23A 50x speedup is pretty cool in its own right. Kudos. However, I wonder if this isn't treating a symptom versus a root cause. Is saving that 5s round-trip so common in your workflow that you needed to optimize it, and would it be more productive to refactor the app so you and collaborators are working on different files? Also, this has the entirely valuable guidance that pushing to a local server is much faster than…
http://xkcd.com/1205/ If you pull 10 times a day (conservative for me) then you’ll save ~5 hours over a year.
But couldn't it very well take more than 5 hours to set this up?
Re: Speed Up Git Pull
#24Re: Speed Up Git Pull
#25[deleted]
Re: Speed Up Git Pull
#26...and keep your development copy of the project on ramdisk. Have a script that you launch as you start work that makes the ramsdisk and puts files from persistent location there using rsync, then periodically launches rsync to copy changes you make on our ramdisk back to persistent location. I used this setup for almost a year. It saved me lot of time and sanity.
Does this buy you that much over a SSD?
Re: Speed Up Git Pull
#27Re: Speed Up Git Pull
#28Re: Speed Up Git Pull
#29...and keep your development copy of the project on ramdisk. Have a script that you launch as you start work that makes the ramsdisk and puts files from persistent location there using rsync, then periodically launches rsync to copy changes you make on our ramdisk back to persistent location. I used this setup for almost a year. It saved me lot of time and sanity.
Does this buy you that much over a SSD?
Not sure. I was using it on a laptop with spinning rust for fairly large rails project.
Re: Speed Up Git Pull
#30...and keep your development copy of the project on ramdisk. Have a script that you launch as you start work that makes the ramsdisk and puts files from persistent location there using rsync, then periodically launches rsync to copy changes you make on our ramdisk back to persistent location. I used this setup for almost a year. It saved me lot of time and sanity.
Does this buy you that much over a SSD?
swap on ssd is (pseudo and slower) increased ram on big needs.
Example: $5 digital ocean droplet (comes without swap, but it's over SSD, so you can create a swap file, and is less painful than mechanical swap).