With Rhythmyx 6.7 - what will make it perform at its best in terms of hardware ? Is it Memory OR Number of CPUs / PRocessor speed that make the biggest different ?
We are looking to decide what hardware we need to buy and want to make sure we get the best performance we can. Looking at either 8 or 16GB RAM but not sure if this is overkill and whether its actually CPU speeds that make more of a difference.
Please advise.
6.7 introduced multi-threaded publishing, with one thread per available cpu. Increasing from the default of 2 cpus to 8 drastically decreased the total publishing time for us. Although, I should add that we’re publishing out 17G nightly, so fast publishing is a necessity. Perhaps your publishing volume doesn’t warrant the concern.
As for memory, last I checked, Linux 32-bit JVMs are limited to 2 GB of memory allocation. On Windows 32-bit, I think they’re limited to 1.5 GB. I think Sun Solaris may support 3 GB allocations, but Sun has recently rearranged their support contracts, corralling people into support contracts. Of course, I don’t know all the details about every JVM on every OS. Our shop only runs open source, so my own research was limited in scope. Furthermore, we run our databases on separate servers. If you’re going to be putting the whole production kit and caboodle on the same box, I think you’re in a different ball park than us.
If you’re running development, pre-production, and production, I’d suggest that you either buy one beefy box and bring up 3 identical virtual environments, or buy three identical boxes. This will drastically simplify the process of refreshing devl and pprd from your prod instance. It’ll also help you avoid issues with port conflicts between the application instances.
In 6.7 you will see the biggest increase in publishing performance by increasing the number of CPU cores available we opted for dual quad core Intel® Xeon® CPU X5550 @ 2.67GHz which also support hyper threading which in theory you could run 16 publisher threads. In practice we only run about 12. It is more about the number of cores rather than the speed of the processor.
One thing to note you need to make sure that your database is able to cope with the increased load from so many publisher processes