I am looking to build additional render nodes for vray for rhino for small arch office so happened upon this thread, though I would share our setup-
We have a total of 6 comps, and typically do distributed rendering during office hours while everyone is working on said computers in Revit or Autocad. I have a 4770k workstation, as well as one other in the office, both with 32 gb ram. We have 2 amdfx6300 / 16 gb ram and 2 amdfx4300 / 16 gb ram. Occasionally a render craps out because one computer kind of 'eats it' and all render buckets turn black, but generally this set up works really well. Of course the hyperthreaderd intels blow the amd's out of the water rendering, but it's what we've got that balances rendering needs with general office needs. We run software in the background to limit how much cpu & ram the DR spawner can use on the nodes, (especially if its a node where user is working in a large revit file). I think intel hyperthreading is a must for the workstation, especially if you intend to keep working while you are rendering. Though the workstations have 32 gb ram, we always limit vray in the options to 8gb ram. DR spawner seems to take a lot, and we've realized that if we want the ability to do cpu rendering while working in other 3d applications, that is the magic number. In contrast, I personally have a 5820k at home with 32gb ram and nvidia gtx 970, which handles big files and grasshopper better than work comp, and handles unreal engine really well also (though I think you are better with 4790k, as that is fastest for single threaded applications). After working in the offfice, its painful how long renders take on one machine, even with 12 hyperthreaded cores. My boss paid $600 or so for each AMD machine in the office, and I am definitely of the mindset that the more cores you can get for the dollar the better. Anyway, different cpus seem to work fine together, the comp that gives us the most trouble is one AMD6300 running windows 8 (we just got it, but will be buying a win7 license bc of autocad/revit issues on it), but even it does what it is supposed to 80% of the time for distributed rendering.