While 1280 files isn’t exactly small, it’s not really big either. Big as in where incremental builds really show their shine. This might be approaching niche b

While 1280 files isn’t exactly small, it’s not really big either. Big as in where incremental builds really show their shine. This might be approaching niche but I’ve seen a few mega-projects with 100 times more than that (also mostly due to vendored deps). You really don’t want to read 10G from disk for every incremental build. The actual sha computation isn’t the bottleneck, disk is. Ninja on the other hand, using mtime, handles this without a sweat. The best solution would probably be to integrate the change detection with git, it is already content addressable and has lots of other smart things built in to make it fast.