TAP TITANS 2 OPTIMIZER 2.11 UPDATE
TAP TITANS 2 OPTIMIZER 2.11 CODE
TAP TITANS 2 OPTIMIZER 2.11 PC

And with somewhat degraded performance on super heavy scenes(hundreds milions poly + displacements etc). I use vray for 13 years, it scales this CPU pretty much linearly on normal scenes. Other render engines scale much better with this CPU in very same environment, but mantra don`t…. We know it has its limits on mem bandwidth,latency, and terrible windows scheduler, but that`s it. And i`ll be bold, lets not blame this on completly on CPU. Pretty much no difference between 32 and 64 cores. Scaling with cores is bad in windows mostly. That goes for benchmarks on sims, or rendering(mantra, vray,corona,) Now to mantra.

TAP TITANS 2 OPTIMIZER 2.11 UPDATE

I have seen absolutely zero speed improvement after Dynamic Local Mode update using Ryzen Master. Mantra speed is scaling so much better on linux too. I get 10-30% better speeds in pyro/flip/grain etc on Linux Mint compared to win 10. Windows performance, compared to Linux is much worse, pretty much in every task.

I have 2990wx 128gb ram and been using it for about 2 months now, 24/7 sims and rendering. 2) Run multiple mantra jobs with a lower thread count, which reduces the performance loss from the third point (but still runs into performance issues from the first. 1) run the optimum number of threads for the job (often needs a bit of testing to determine this). As a user, you can do a few things to fix this. This is a problem which gets worse as the # threads increase as well.

TAP TITANS 2 OPTIMIZER 2.11 CODE

Even getting rid of all exclusive resources in the code will still have waits at the system level. Anything that needs exclusive temporary access to a resource can chip away at the speedup as threads wait. This is known as Amdahl's law, and the only way to get around it is to optimize B as much as possible. You'll get a nice exponential falloff settling onto some plateau where it doesn't really improve much anymore. What happens is that the total time begins approaching time(B), the single threaded stuff. And at 64, it's 1.5% (but not really, ‘cause SMT isn’t 2x faster). Assuming ideal scaling (more on that in a moment), at 32 threads it's taking 3% of the time of 1 thread. Total time = time(A)/#threads + time(B) As the number of threads increases from 1, the time taken to do A halves, halves again, etc. And after some tweaks in bios (not direct CPU overclocking) Mantra - 32 core, SMT on - 2.19 min. When active 16 cores and SMT off - 2.30 min. When SMT off with 32 active cores, mantra work much faster - 1.53 min vs 2.54 (SMT on). Interesting situation with SMT (simultaneous multithreading) technology. At same time Arnold render, in Maya 2018 update 4, work more predictably. But! When active only 16 cores (32 thread) mantra render work faster. Problem - mantra render work slower when all 32cores (64 threads) is active.

TAP TITANS 2 OPTIMIZER 2.11 PC

First of all - PC spec: Threadripper 2990wx, 128 Gb memory, GTX titan X.

Tap titans 2 optimizer 2.11