4 ms·
I did just over a decade in chip design. Versioning large files in that domain is commonplace and quite sane. It can take wallclock days of processing to produc
by iaresee 3y ago
I did just over a decade in chip design. Versioning large files in that domain is commonplace and quite sane. It can take wallclock days of processing to produce a layout file that's 100's of MBs. Keeping that asset in your SCC system along side all the block assets it was built up out of is very desireable.
Perforce handled it all like a champ.
People who think large files don't belong in SCC are...wrong.
- ChrisMarshallNY 3y agoThat's why Perforce is still the SCM of choice for a lot of creatives. I don't know if they still do it, but Unreal used to ship a Perforce license with their SDK.
- nightfader 3y agoThat's also why perforce is slow as heck unless you throw massive resources at it. I also work in the chip industry BTW.
- ChrisMarshallNY 3y agoI don't like it (but used it for many years). I love Git, but, then, I don't have a workflow that would benefit from Perforce.
- iaresee 3y agoI mean "massive resources" is just de rigeur across the chip industry now. The hard in hardware is really no longer about it being a physical product in the end.
- beebeepka 3y agoI've only used Perforce for two years and it didn't feel slow at all. The company wasn't exactly throwing money at hardware.
- pama 3y agoI occasionally used to start a sync, go get coffee, chat with colleagues, read and answer my morning email, browse the arxiv, and then wait a few more minutes before I could touch the repo. In retrospect, I should have setup a cron job for it all, but it wasn’t always that slow and I liked the coffee routine. We switched to git. Git is just fast. Even cloning huge repos is barely enough time for grabbing a coffee from down the hall.