@Patrick, AFP is "broken" in that is can no longer sustain high-bandwidth network transfers. You can some of my original testing via this thread, but the long story short:
- Via 10.6 Server, our AFP network read/writes, on average, are 95 MB/s reads, 70 MB/s writes.
- Via 10.8 Server, our AFP network read/writes, on averaige, are 95 MB/s reads, 95 MB/s writes.
- Via 10.9 Server, our AFP network read/writes, on average, are 40 Mb/s reads, 95 MB/s writes.
I haven't updated the thread posted above, lately, but for my continued testing (when Apple was responding to my bug reports), I ended up taking one of our Xserves, along with a Mac mini, for dedicated testing. The Xserve is dual boot between 10.8 Server and 10.9 Server, so the same hardware, network, client, etc. is used for all testing at this point (and, via Apple, my testing now includes a wide range of tests, from manual clocking of 10 GB dmg files right up through a whole series of command line and GUI-based network speed testing tools). Across the board, the results are always the same—toss 10.9 Server into the mix, and high-bandwidth network transfers can't be sustained.
For less intense network transfers, this issue is probably never seen (as it takes about 45 seconds before the network transfer hits the wall then drops to a crawl), but with high-bandwidth transfers, it's unbarable. And since high-bandwidth network transfers is required, for us, I'm unable to upgrade to Mavericks Server knowing our transfer times would take twice as long as they do now. I've been dealing with this issue for almost two months now (at times, running tests on a daily basis, though now, I've pretty much given up on Mavericks Server, only testing when a new seed has been released, and have moved-forward with Mountain Lion Server, since I don't need SMB support).
So, that's what I mean when I say AFP is "broken". 8)
Also note: From my testing, this actually seems to be an issue with Mavericks Server, as using Mavericks client or Mountain Lion Server or Mountain Lion client (or earlier client/server versions), there are no issues. It's only when adding Mavericks Server into the mix does the issue present itself.