pyGIMLi and NUM_THREADS about gimli HOT 7 CLOSED

Change default behaviour. Will be live after the next core update.

export OPENBLAS_NUM_THREADS=12 && python -c 'import pygimli as pg; print(pg.core.threadCount())'
12
unset OPENBLAS_NUM_THREADS && python -c 'import pygimli as pg; print(pg.core.threadCount())'
16

from gimli.

We maybe could change this that he only sets this environment variable, if its not already specified by the user?

from gimli.

This circumvents the issue (mostly):

import pygimli as pg
pg.setThreadCount(1)

but still, I would not expect an import to mess with my variables.

from gimli.

For conveniance reasons, the core extension of pygimli sets OPENBLAS_NUM_THREADS to number of cpu -2 right on initializing. You can change it back after importing pygimli with pg.setThreadCount(1)

from gimli.

I see. But when the number of CPU is 256 on a shared cluster, that is a very inconvenient default IMHO.

I would prefer what you say afterwards. IF there is a user set env variable, it should be respected.

from gimli.

And maybe also a MAX (no need to set the nthread to 254).

from gimli.

Great, like it, thanks for the quick turnaround! 8 or 16 was exactly what our HPC expert here also suggested as maximum, as openblas won't be much efficient beyond that number.

from gimli.