GPU RAM usage for simple camera tracking

Good afternoon (o;

I am trying a simple camera tracking example with a 60 frames footage in 1080p...
Minimum feature set is set to 0.1 and the rest are the default settings...think it's the lowest possible setting...

Tracking forth and back is done fine...but fills up the 6GB quickly...so the out of GPU memory is popping up and I have to kill resolve studio manually...

If I leave the tracker preview is off, the GPU error popups only if I select the in the viewer...

Do I need 128GB GPU RAM to do a simple camera tracking on resolve studio 15.0.0 Linux?

Also tried different settings with Auto/Cuda/OpenCL or Fusion on CPU only...still no joy....


During calculation I see:

Code: Select all

Fri Aug 24 16:33:11 2018       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.77                 Driver Version: 390.77                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:01:00.0  On |                  N/A |
|  7%   56C    P2    56W / 120W |   2370MiB /  6075MiB |     81%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0       646      G   /usr/lib/xorg/Xorg                           294MiB |
|    0      1186      G   /proc/self/exe                                43MiB |
|    0      6378      G   nvidia-settings                                0MiB |
|    0      8965    C+G   /opt/resolve/bin/resolve                    2063MiB |
+-----------------------------------------------------------------------------+


A second later when it is finished and it should show the result in the left viewer from the tracker node:

Code: Select all

Fri Aug 24 16:33:12 2018       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.77                 Driver Version: 390.77                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:01:00.0  On |                  N/A |
|  8%   56C    P2    33W / 120W |   6060MiB /  6075MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0       646      G   /usr/lib/xorg/Xorg                           294MiB |
|    0      1186      G   /proc/self/exe                                43MiB |
|    0      6378      G   nvidia-settings                                0MiB |
|    0      8965    C+G   /opt/resolve/bin/resolve                    5717MiB |
+-----------------------------------------------------------------------------+


Even merging two 1024x1024 png in resolve fusion with a short clip (10 secs) occupies:

Code: Select all

|    0     12244    C+G   /opt/resolve/bin/resolve                    4921MiB |
+-----------------------------------------------------------------------------+

Try to switch off the GPU and try again.
I observe only 30% activity of the GPU when doing 3D camera tracking and solves, while the CPU cores are running at 60-70%.

I tried using the CPU for Fusion only...bombs also with camera tracker and shows high GPU RAM usage on Linux...but only when I want to display the 3d scene in the left viewer...

See only high CPU usage when optimising media....


For simple clips and with just a color/brightness correction in fusion it occupies around 4 - 5GB GPU RAM at least...

Now a tracking of a 30 frames clip was successful...and when I clicked on the export tab resolve studio just quit with no error messages...

Linux version seems GPU hungry and quite buggy...

Got doubgt if a 11GB GPU would be any better or just filled quickly as well until it crashes...

I checked GPU memory usage and surprisingly, even if Fusion is set to use the CPU, the memory of my GPU is getting used close to 100%. It doesn't crash, though.
This doesn't seem to depend on resolution, I see the same with HD or UHD.

P.S.
I also tried the same in Fusion standalone, and to my surprise the usage of VRAM was much lower, around 20-25%. It seems that Resolve is somehow using the VRAM to operate Fusion in it's page. So, for now I'd use the standalone for such tasks if there are problems. After all, camera tracking is a demanding task and the integration of Fusion is still a work in progress.

So I assume this has something to do with Fusion being integrated since resolve studio 15...

Was today able to render a 1080p clip of 44 seconds length in total (includes around 12 individual clips where each one was color/brightness corrected in fusion). Some of the clips stabilized...short PNG overlays at the beginning who moves sideways out with an elevator door...no GPU RAM full error, though the 6GB were mostly filled up to 99% though Fusion did work in CPU...

Now another quick test with particle dissolve...and bomb...you can quit the application, window closes, but it runs forever, so you need to kill it always manually after a GPU error...

I haven't done anything in Fusion alone, nor do I intend to buy Fusion Studio as it seems it will disappear pretty soon.

Attached the node fusion particle example and GPU settings which lead to the GPU error..

Could you please post the script for that particle system to test it here on my hardware?

How can I extract this as a script?

I did this following a vido tutorial....where you could als down it as a macro...
with the downloaded macro it went fine...well tested just one time

Click on File- Export Fusion Comp.

I'd like to work with the same values to compare.

Here it is..and thanks for the great help

My main problem is not that the newly acquired 1060/6GB card isn't enough. I am just unsure if I build a new macOS or Linux machine with a 1080/11GB it won't be different...and dual GPU won't help at all, not memory nor performance wise...though this might have changed in DRS 15...

I can confirm that this particle script crashes the Fusion page with a GPU RAM full error, even with 8 GB VRAM. The same particle script works fine in the standalone version with less than half of the VRAM in use.

I'd use Fusion Connect for now.

I did some more testing and found an interesting workaround, it seems:
viewtopic.php?f=21&t=78349

It is now worse with version 15.0.1 on Linux...

GPU memory full error shows even when GPU memory is around 50 - 60%...

Guess this won't be fixed in the next couple of months...so no fancy Fusion effects at all then....

Yes, I went back to Fusion standalone.