This week we continue the development of a new benchmark and dive into scripting within 3ds Max
An ongoing series on creating a benchmark, from inception to completion. This week, identifying areas of 3ds Max that hardware creates slowdowns or bottlenecks.
Here at Puget Systems, it is our goal to perform realistic testing on the software packages we tailor our workstations toward. Sometimes this is easy, sometimes it is harder… and sometimes a software maker already provides their own benchmark tool. That is the case with Maxon, makers of Cinema 4D, as well as the free benchmark, took Cinebench. To determine whether we should use it, though, we have to ask some questions. Is Cinebench really a good benchmark for Cinema 4D? How do the tests it runs relate to real-world performance?
We test a lot of software here at Puget Systems, and in most cases what we are looking for is what hardware lets a given program run the fastest – or in some cases, what is the most cost effective. If you can get 95% of the best possible performance for half the price that it would cost to get a full 100%, for example, that is often a compelling way to go. However, ANSYS Mechanical (and FLUENT) present a different challenge: how can you get the best performance within the limitations of the ANSYS licensing model?