threads
option is overridden before passing it to number-processes
arg
#3218
-
Hello, first of all I want to thank you for this amazing library. When running
I noticed that I was wondering if this is intentional, and if it's possible to bump it up? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Quoting from #1408 (comment) (@lonvia is one of the maintainers of osm2psql and maintainer of Nominatim) The number of processes was set to 1 intentionally. The osm2pgsql import itself is not multithreaded (or rather it is but not in any way that is influenced by this parameter). The only phase that is parallel is indexing. In this phase a high number of threads tends to be counter-productive. In my experience it is better to increase the maintenance memory to make creating a single index faster than increasing the number of parallel threads. |
Beta Was this translation helpful? Give feedback.
Quoting from #1408 (comment) (@lonvia is one of the maintainers of osm2psql and maintainer of Nominatim)
The number of processes was set to 1 intentionally. The osm2pgsql import itself is not multithreaded (or rather it is but not in any way that is influenced by this parameter). The only phase that is parallel is indexing. In this phase a high number of threads tends to be counter-productive. In my experience it is better to increase the maintenance memory to make creating a single index faster than increasing the number of parallel threads.