Here are my results from a recent endgame match where all engines play all others at 4" per move over 30 pseudo-random endgame positions repeated. Shredder uses the fast 450MB Shredderbases, Nalimov's 3-4-5 EGTB's where possible, and IvanHoe uses the RobboTripleBases.
Worth noting is that IvanHoe did not have access to TotalBases, only TripleBases. I assume that if it had, its rating would be even higher.
Next up, a 60R RR with Houdini 1.01, Shredder 12, Deep Rybka 4, Stockfish 1.7.1, Naum 4.2, Spark 0.4, and Zappa Mexico II... identical conditions except starting from late opening, early middle game positions.
I think it would be worth it to test with alternate tablebase usage as well. I am never sure how developers come to set these default settings, to maximize performance in games or analysis. In this case I wonder how using tablebases rarely with a constant time per move time control as opposed to a repeating time control could in influence the results. Anyways, it's on my list of things to do.
You get the counterintuitive impression that R4 might perform better with no tablebase usage at all. Not enough games to draw conclusions when the ratings are so compressed and margin of error's so high, but it makes you wonder...