#general
- b
billowy-alarm-80641
09/14/2015, 9:19 PMwe have it optimized w/ a custom version of git, so it's pretty fast - b
billowy-alarm-80641
09/14/2015, 9:19 PMdefinitely less than a minute - b
billowy-alarm-80641
09/14/2015, 9:19 PMit was much slower before the optimizations - a
ancient-stone-50795
09/14/2015, 9:19 PMhow much slower? - b
billowy-alarm-80641
09/14/2015, 9:20 PM10 - 30 mins, depending on the state of your repo - a
ancient-stone-50795
09/14/2015, 9:20 PMwow. - b
billowy-alarm-80641
09/14/2015, 9:20 PMgit gc was firing a lot - b
billowy-alarm-80641
09/14/2015, 9:20 PMwhich really slowed things down - m
mammoth-pharmacist-54215
09/14/2015, 9:20 PMMakes me glad I joined after that was optimized simple smile - a
ancient-stone-50795
09/14/2015, 9:21 PMWhat is the state of those git optimizations? Is it your own internal copy of git or is it open sourced anywhere? - b
billowy-alarm-80641
09/14/2015, 9:21 PMour own internal copy of git, unfortunately - b
billowy-alarm-80641
09/14/2015, 9:21 PMthere has been talk about open sourcing - b
billowy-alarm-80641
09/14/2015, 9:21 PMbut I'm not sure of the status of that - m
mammoth-pharmacist-54215
09/14/2015, 9:21 PMI thought we were trying to get our patches pushed upstream - w
witty-crayon-22786
09/14/2015, 9:22 PMsome of them, yea. - b
bored-art-40741
09/14/2015, 9:23 PMHeads up, Mateo did some very thorough perf testing of isolated vs global in our repo - b
bored-art-40741
09/14/2015, 9:23 PMWe've found several issues, probably blockers - b
bored-art-40741
09/14/2015, 9:23 PMWe're going to put together a list with some precise repros - w
witty-crayon-22786
09/14/2015, 9:24 PMgreat, thanks - w
witty-crayon-22786
09/14/2015, 9:24 PMdoing a bit of profiling today as well - h
happy-kitchen-89482
09/14/2015, 11:31 PMCan we have those git optimizations please? simple smile - b
billowy-alarm-80641
09/15/2015, 12:56 AM@happy-kitchen-89482 @ancient-stone-50795 I sent a note to the internal git folks about it. We'll see what they say. - a
ancient-stone-50795
09/15/2015, 1:02 AM@billowy-alarm-80641: Thanks. There is some FUD that git won’t be able to scale as we grow and word leaked out that Twitter takes 30 minutes to do a git pull. This was brought up today in the middle of a meeting where we were discussing scaling concerns in the repo. - a
ancient-stone-50795
09/15/2015, 1:02 AMI was surprised to learn there was some truth to it to be honest. - b
billowy-alarm-80641
09/15/2015, 1:03 AMyeah, early 2015 wasn't too hot. 😐 - m
mammoth-pharmacist-54215
09/15/2015, 1:03 AMI’m chatting with Sims (from our source team) about it atm - b
billowy-alarm-80641
09/15/2015, 1:03 AMmaybe an ex Tweep at Square that was quoting that number - a
ancient-stone-50795
09/15/2015, 1:03 AMAn ex tweep friend of a square that worked at Twitter for a grand total for 3 months. - b
billowy-alarm-80641
09/15/2015, 1:03 AMUg. - a
ancient-stone-50795
09/15/2015, 1:04 AMI had similar problems working with perforce at Salesforce, it would take a very long time to get back to master, but that was due to a whole host of problems.