Moldflow Insight should be updated to properly query processor count on modern server platforms.   We recently attempted to do trial runs on an Amazon AWS server with Insight installed in order to see how well performance scaled with CPU counts increasing (it's very easily to increase resources on the fly), and found that it routinely detected only half of the available processors, and all Synergy threads combined would not exceed 50% CPU utilization, regardless of the number of jobs running or parallelization settings.  Assuming it was a bug with the AWS platform I installed Insight on a bare-metal server on-site (we run on virtual servers in production) and found the same issue, before stumbling into an HPE customer advisory describing the issue:   https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-c04650594   Updating the BIOS setting in the advisory is possible (and there is presumably an equivalent on other brands like Dell), but does come at a performance penalty.  I don't believe it's possible to make this change on the AWS platform, for an organization attempting to use remote servers for solves.   The obvious benefit of this is to double the available CPU resources available on a modern server platform (the issue began in ~2015, with the introduction of the Intel E5-26XX v3 series CPU).  With one or two jobs running it may not make a huge difference, but Moldflow could be highly scalable on the token-flex model since there are an unlimited number of solves on a single Insight instance.  For example, a server with 64 processors could easily be running 8 jobs with ~8 processors available per job. Show More