3 ms·
This has been the way to get performance on a large Git repo for over a decade now, just not built into Git. It provides very good improvements even in environm
by sulam 4y ago
This has been the way to get performance on a large Git repo for over a decade now, just not built into Git. It provides very good improvements even in environments that aren't the fastest, like laptops.
- saagarjha 4y agoSee my point isn't whether this makes Git faster (it probably does) but it may have a performance impact on the rest of the system.
- sulam 4y agoWe deployed a system like this across hundreds of engineers in a reasonably sized monorepo and had zero complaints about system performance. While I don’t know the underlying architecture of inotify/etc, it seems to be very efficiently implemented.
- rkangel 4y agoIt is of course not turned on by default. I don't know how bad the performance hit is, but it's an option so you get to choose the tradeoff. Either your git operations are slow or you take the small hit on all operations. If you spend all of your time working in a big repo it's probably going to be worth it.