I'll have a deeper look into this. In the meantime it would be helpful
to learn from you in more detail what nvidia-smi tells you about the GPU
memory usage in the different steps of your test, especially before and
after you get your test run failing for the first time.
For your information here on my system it typically looks like this:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.111 Driver Version: 384.111
|
|-------------------------------+----------------------+----------------------+
| 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 |
| 3% 50C P8 10W / 120W | 173MiB / 6065MiB | 0%
Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU
Memory |
| GPU PID Type Process name Usage
|
|=============================================================================|
| 0 3563 G /usr/bin/X
93MiB |
| 0 3977 G kwin_x11
19MiB |
| 0 3992 G /usr/bin/krunner
1MiB |
| 0 3994 G /usr/bin/plasmashell
53MiB |
| 0 4035 G /usr/bin/kgpg
2MiB |
+-----------------------------------------------------------------------------+
When darkttable GUI is running and idle it has an additional permanent
requirement of about 63MB. During image processing GPU memory of
darktable goes steeply up but always returns to the idle value
afterwards. When terminating darktable there should be no traces of it
left in the output of nvidia-smi.
Ulrich
Am 25.05.2018 um 07:34 schrieb Matthias Bodenbinder:
Am 25.05.2018 um 07:10 schrieb Ulrich Pegelow:
I have put all relevant files on dropbox:
https://www.dropbox.com/sh/yarghqgncirjd0w/AADUNyFGaGUpyBTDil_qaxsUa?dl=0
There you will find a script test-CR2.sh which infinitly calls darktable-cli
with the big 5Ds file. And it creates a log file for this. I have attached 2 of
those log files.
The first log file 5Ds-infite-30762-15-runs-no-issue.log.gz is from the start
of the test, where darktable-cli is runnming just fine 15 times. Then I enter
the darktable GUI and export 26 of my Canon 6D files. I exit the GUI and start
test-CR2.sh again. I had to repeat this cycle for 4 times before the issue
occurs. The result is shown in the second logfile:
5Ds-infite-2750-3-runs-with-issue.log.gz
I have been using opencl_memory_headroom=500 for this test. I am using DT
2.4.3. In addition I have firefox 60.0.1, thunderbird 52.8 and three
gnome-terminals open. My system is running on Manjaro testing with kernel
4.16.11.
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
