We are planning to store frequently updated text and graphics in a version control system. It's not source code, but it is mostly text files. No single object is "large", but the size of the repo would grow large with frequent updates.
How can I guess how large in terms of version history is too large to make git practical to use, as opposed to another version control system.
Update: This isn't an answer to the question. But, for my purposes it would probably work to use clone --shallow-since=... based on observing how the repo grows over time, without having an answer to "how many objects".