I guess I should have read a few materials and kept up to date about RobboBase happenings. I could have given you more decent estimates.
First the ROBBO_BASE_BRIEF:
The totality of 6s will emerge in many days or weeks, and you need to tune the memory with 32GB in RAM enough but edgy.
A rule is to multiply by 150-200x for each next piece. The 5 piece take to build in nearly 15 hours of cpu at 3.41GB, and the 6 piece in 3-4 months of cpu when you have the memory (RAM) at 476GB.
So it seems that they take 3-4 cpu-months to build the 6s with 32GB of RAM [though my accounting yields that even 12GB should be OK, though maybe I'm disregarding disk access/caching with promotions], as opposed to downloading 476GB. From their wiki, they claim to have a download site set up for which the throughput can be as high as 10MB/s. At the more reasonable rate of 1MB/s it would take about a week, so my guess is that downloading will win on a strict time comparison in most cases. This should be true for any of the tablebase systems.
GCP was building a single 6 piece endgame in about a day, which seems to indicate around a calendar year to build them all. The Nalimov algorithm is slightly inferior to what (I presume) the RobboBases are using for many cases, as I think it uses the "grandfather" system as opposed to the "counting outs" system (see
http://home.hccnet.nl/h.g.muller/EGTB.html for more about this, and he seems to have a 7-piece Leapfrog generator mentioned now). However, the main bottleneck for 6 pieces is I/O in any case, even with your 12GB of RAM.
Reading the original post again, I might mention that
wget can be likely queued up to grab multiple files when downloading.