I've been continuing to post the occasional article over at the blog run by my day job.
A few recent articles include:
- The Distributed Perforce Service
A Distributed Perforce installation offers a number of significant benefits. If you're trying to decide whether to deploy or not, ask yourself the following questions.
- The Simple Magic of the Forwarding Replica
A Forwarding Replica combines some of the best features of the Perforce Proxy with some of the best features of the Perforce Replica.
- You're Probably Not Running Enough Archive Pull Threads
New files tend to be added to a Perforce server in batches. It's relatively rare to see a changelist with just a single file in it; changelists often have dozens or hundreds of files, and changelists with thousands of new files are not uncommon.
- Taming your Spec Depot to keep it Under Control
The Perforce server's Spec Depot feature is very handy. If you don't already have a Spec Depot, you should!
- 2013: A Busy Year for the Server!
As we near the end of 2013, it's exciting to look back at this year. You can make a strong argument (and I do!) that this has been the busiest and most eventful year in the history of the Perforce server.
- Some of the Wonders of the Sync Command
During the 'p4 sync' command, the server and the client are both busy: the server is sending files to the client as fast as the network connection will allow, and the client is writing those files to its filesystem as fast as the workstation will allow. And each time the client finishes one of those files, it sends an acknowledgement back to the server so that the server will know.