of environment variables • Obtaining information from the .condarc file • Configuring number of threads Overview The conda configuration file, .condarc, is an optional runtime configuration file that (pypirc) • PyPI repository to upload to (conda-build 3.0+) (pypi_repository) • Configuring number of threads 56 Chapter 1. User guide conda Documentation, Release 23.3.1.post2+bdcba5dd0 Specify conda-build that environment. Configuring number of threads You can use your .condarc file or environment variables to add configuration to control the number of threads. You may want to do this to tweak conda to

of environment variables • Obtaining information from the .condarc file • Configuring number of threads Overview The conda configuration file, .condarc, is an optional runtime configuration file that (pypirc) • PyPI repository to upload to (conda-build 3.0+) (pypi_repository) • Configuring number of threads 56 Chapter 1. User guide conda Documentation, Release 0.0.0.dev0+placeholder Specify conda-build that environment. Configuring number of threads You can use your .condarc file or environment variables to add configuration to control the number of threads. You may want to do this to tweak conda to

‘server’ requesting pages and rendering them for other threads that need them, then the library is only ever being called from this one thread. Other threads can still be used to handle UI requests etc, but more complex case; where we genuinely want to call the MuPDF library concurrently from multiple threads within a single application. MuPDF can be invoked with a user supplied set of locking functions these to take mutexes around operations that would conflict if performed concurrently in multiple threads. By leaving the exact implementation of locks to the caller MuPDF remains threading library agnostic

Installation What is a Task Queue? Task queues are used as a mechanism to distribute work across threads or machines. A task queue’s input is a unit of work called a task. Dedicated worker processes constantly ORM (exp), Amazon SQS, (exp) and more… Concurrency prefork (multiprocessing), Eventlet, gevent threads/single threaded Result Stores AMQP, Redis memcached, MongoDB SQLAlchemy, Django ORM Apache Cassandra celery[eventlet]: for using the eventlet pool. celery[gevent]: for using the gevent pool. celery[threads]: for using the thread pool. Transports and Backends celery[librabbitmq]: for using the librabbitmq

Installation What is a Task Queue? Task queues are used as a mechanism to distribute work across threads or machines. A task queue’s input is a unit of work called a task. Dedicated worker processes constantly (multiprocessing), • Eventlet, gevent 2.2. Getting Started 7 Celery Documentation, Release 3.1.25 • threads/single threaded • Result Stores • AMQP, Redis • memcached, MongoDB • SQLAlchemy, Django ORM • Apache celery[eventlet] for using the eventlet pool. celery[gevent] for using the gevent pool. celery[threads] for using the thread pool. 10 Chapter 2. Contents Celery Documentation, Release 3.1.25 Transports

‘server’ requesting pages and rendering them for other threads that need them, then the library is only ever being called from this one thread. Other threads can still be used to handle UI requests etc, but more complex case; where we genuinely want to call the MuPDF library concurrently from multiple threads within a single application. MuPDF can be invoked with a user supplied set of locking functions these to take mutexes around operations that would conflict if performed concurrently in multiple threads. By leaving the exact implementation of locks to the caller MuPDF remains threading library agnostic

per-request to stabilize their behavior. See https://github.com/Pylons/waitress/pull/300 Waitress threads have been updated to contain their thread number. This will allow loggers that use that information See https://github.com/Pylons/waitress/pull/239 Fix the queue depth warnings to only show when all threads are busy. See https://github.com/Pylons/waitress/pull/243 and https://github.com/Pylons/waitress/pull/247 forwarded-port' \ --log-untrusted-proxy-headers \ --clear-untrusted-proxy-headers \ --threads ${WEB_CONCURRENCY:-4} \ myapp:wsgifunc The proxy config informs Waitress to trust the forwarding

per-request to stabilize their behavior. See https://github.com/Pylons/waitress/pull/300 Waitress threads have been updated to contain their thread number. This will allow loggers that use that information See https://github.com/Pylons/waitress/pull/239 Fix the queue depth warnings to only show when all threads are busy. See https://github.com/Pylons/waitress/pull/243 and https://github.com/Pylons/waitress/pull/247 forwarded-port' \ --log-untrusted-proxy-headers \ --clear-untrusted-proxy-headers \ --threads ${WEB_CONCURRENCY:-4} \ myapp:wsgifunc The proxy config informs Waitress to trust the forwarding

per-request to stabilize their behavior. See https://github.com/Pylons/waitress/pull/300 Waitress threads have been updated to contain their thread number. This will allow loggers that use that information See https://github.com/Pylons/waitress/pull/239 Fix the queue depth warnings to only show when all threads are busy. See https://github.com/Pylons/waitress/pull/243 and https://github.com/Pylons/waitress/pull/247 forwarded-port' \ --log-untrusted-proxy-headers \ --clear-untrusted-proxy-headers \ --threads ${WEB_CONCURRENCY:-4} \ myapp:wsgifunc The proxy config informs Waitress to trust the forwarding

private.conda.channel Configuring number of threads You can use your .condarc file or environment variables to add configuration to control the number of threads. You may want to do this to tweak conda to increase the number of threads to shorten the time it takes for conda to create environments and install/remove packages. repodata_threads • Default number of threads: None • Threads used when downloading verify_threads • Default number of threads: 1 • Threads used when verifying the integrity of packages and files to be installed in your environment. Defaults to 1, as using multiple threads here can