Tweet
Displacement, random render times on Dual Xeon
Hello,
about a week ago I bought a new machine.
The configuration for the new machine is:
Dual Xeon E5-2690 V3
Asus Z10PE-D8 WS (m/b)
32GB RAM DDR4 ECC
Quadro K4200
An SSD for system disk plus a few HDs
For comparison reasons the old machine is:
i7 965x (@3.55GHz)
Asus P6T Deluxe (m/b)
12GB RAM DDR3
An SSD for system disk
To the problem now.
I am using 3ds max 2015 and I have installed Vray 3.10
In one of my scenes, that I used as a benchmark to check vs my old machine, I have a big displacement map (its a 2 color B&W map of earth actually).
The old machine in a particular frame (I chose it for benchmark reasons) I got 15mins
In the New machine thats the randomness I am talking about, I get between 2:38 and 3:17
This happens in the displacement calculation stage.
In my old machine that stage takes about 6sec in the new machine takes between 30sec and 1:10!!!
I timed many times that stage.
Then I tried to remake a scene using the same item with the same displacement but without the rest of the original scene's items, lights and textures.
There I got even more strange results.
The old machine gave a 17:18 sec with 8 sec be the displ calculation phase
The new machine took 4:30 with a 25sec (minimum) disp calc phase. Once I got a 4:14. I never got that again.
The cherry on the top of this is that if by affinity I turn off the second processor the displace calculation takes about 15sec and the render time is about 5:40 (far far away from an almost double time)
Its like the second processor barely used and the calculation takes ages.
This sounds more than a bug than anything else.
As core per core the new system is more powerful despite the lower MHz.
Even if the many cores "confuse" somehow the engine of the Vray still this could be made in such away so in that phase will use only a single core.
Thats why I am calling this a bug.
Its really funny that a 6 year old processor calculates the displacement even 10 times faster (as is random and gets that slow) than a fresh Xeon processor, that even core per core is faster.
Please any help will be much appreciated.
PS. I want also to add that, in most scenes that I have test the two machines (with no displacement), the Xeon is about 6 to 7,2 times faster.
about a week ago I bought a new machine.
The configuration for the new machine is:
Dual Xeon E5-2690 V3
Asus Z10PE-D8 WS (m/b)
32GB RAM DDR4 ECC
Quadro K4200
An SSD for system disk plus a few HDs
For comparison reasons the old machine is:
i7 965x (@3.55GHz)
Asus P6T Deluxe (m/b)
12GB RAM DDR3
An SSD for system disk
To the problem now.
I am using 3ds max 2015 and I have installed Vray 3.10
In one of my scenes, that I used as a benchmark to check vs my old machine, I have a big displacement map (its a 2 color B&W map of earth actually).
The old machine in a particular frame (I chose it for benchmark reasons) I got 15mins
In the New machine thats the randomness I am talking about, I get between 2:38 and 3:17
This happens in the displacement calculation stage.
In my old machine that stage takes about 6sec in the new machine takes between 30sec and 1:10!!!
I timed many times that stage.
Then I tried to remake a scene using the same item with the same displacement but without the rest of the original scene's items, lights and textures.
There I got even more strange results.
The old machine gave a 17:18 sec with 8 sec be the displ calculation phase
The new machine took 4:30 with a 25sec (minimum) disp calc phase. Once I got a 4:14. I never got that again.
The cherry on the top of this is that if by affinity I turn off the second processor the displace calculation takes about 15sec and the render time is about 5:40 (far far away from an almost double time)
Its like the second processor barely used and the calculation takes ages.
This sounds more than a bug than anything else.
As core per core the new system is more powerful despite the lower MHz.
Even if the many cores "confuse" somehow the engine of the Vray still this could be made in such away so in that phase will use only a single core.
Thats why I am calling this a bug.
Its really funny that a 6 year old processor calculates the displacement even 10 times faster (as is random and gets that slow) than a fresh Xeon processor, that even core per core is faster.
Please any help will be much appreciated.
PS. I want also to add that, in most scenes that I have test the two machines (with no displacement), the Xeon is about 6 to 7,2 times faster.
)
Comment