billyanok

I ran a test with Blackmagic eGPU using the "jitter_benchmark-v1.0121, strange results.

Blackmagic eGPU @ Radeon Pro 580 8192 MB GPU

I ran a test with Blackmagic eGPU using the "jitter_benchmark-v1.0121, strange results.
GPU Geometry2 half the speed?
GPU Geometry 1 basically same speed?

????

Max 7.3.5 64 bit
MacBook Pro (15-inch, 2017)
OSX 10.13.6
3.1 GHz Intel Core i7
16 GB 2133 MHz LPDDR3

Blackmagic eGPU @ Radeon Pro 580 8192 MB GPU
CPU: 240.4 
GPU Geometry 1: 38.8 
GPU Geometry 2: 59.0 
GPU Pixel Shaders: 206.6 

Built-in Radeon Pro 560 4096 MB GPU
CPU: 162.5 
GPU Geometry 1: 37.1 
GPU Geometry 2: 115.8 
GPU Pixel Shaders: 125.7 

Hey Guys,
I ran a test with Blackmagic eGPU using the "jitter_benchmark-v1.0121, strange results.
GPU Geometry2 half the speed?
GPU Geometry

blackmagic-egpu-test-results

I built Geometry Test 1 with the purpose of seeing the behaviour of replicating multiple instances of the same geometry (jit.gl.multiple). The geometry data is fixed and stored on the GPU using the @displaylist 1 attribute.

On the other hand, Geometry Test 2 was built with the purpose of having a complex geometry (many vertices) that may require to be constantly sent from CPU to GPU (although, in this case the geometry continues to be fixed...).

So, I guess the bottleneck is the communication between CPU and GPU (Thunderbolt). Try to open the geometry 2 subpatch and add "@displaylist 1" at the 3 geometry objects being drawn. The fps should improve dramatically...

Hi Billy.
I'm guessing I know the reason for that.
I built Geometry Test 1 with the purpose of seeing the behaviour of replicating multiple instances of the same geometry (jit.gl.multiple). The geometry data is fixed and stored on the GPU using the @displaylist 1 attribute.
On the other hand, Geometry Test 2 was built with the purpose of having a complex geometry (many vertices) that may require to be constantly sent from CPU to GPU (although, in this case the geometry continues to be fixed...).
So, I guess the bottleneck is the communication between CPU and GPU (Thunderbolt). Try to open the geometry 2 subpatch and add "@displaylist 1" at the 3 geometry objects being drawn. The fps should improve dramatically...


I'm thinking tho' it may not be suitable for general Jitter use as the TB3 port I think maxes out at 22Gbps?

Yes sir, frame rate hit 400fps.
I'm thinking tho' it may not be suitable for general Jitter use as the TB3 port I think maxes out at 22Gbps?
Thank you for your input!
Billy

Blackmagic eGPU test results