Closed trmt closed 1 year ago
Good catch - looks like the blosc_get_nthreads() was only getting called when the blosc_nthreads config was set to zero. Did you get better performance using the number of threads available on the processor?
It was just test run in systemd-nspawn container with cpu limit option. that's why i set blosc_nthreads to zero and caught that error
Good you found that. Setting blosc_nthreads to zero may not be what you want to limit cpu usage though. Zero causes the number of threads to be based on whatever the processor supports. Using a value of one would be the most cpu-limiting choice.
thanks for advice