---
title: "Discussion on \"Gevent celery config I/O bound\" | Hashnode"
description: "Discussion on \"Gevent celery config I/O bound\". When NOT using Gevent (worker_pool\\=[prefork|gthread]), the number of concurrent workers defaults to the number of cores which are effectively the tasks that will be executing in “parallel”.\nThe prefetch multiplier (default 4) is an optimization to r..."
url: "https://hashnode.com/posts/gevent-celery-config-io-bound/694fa3e01b0f9bdaad9aa0a6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Gevent celery config I/O bound](https://blog.danwald.me/gevent-celery-config-io-bound?utm_source=hashnode&utm_medium=feed)

When NOT using Gevent (worker\_pool\\=\[prefork|gthread\]), the number of concurrent workers defaults to the number of cores which are effectively the tasks that will be executing in “parallel”. The prefetch multiplier (default 4) is an optimization to r...

Dec 27, 2025 · 2 min read · blog.danwald.me  
Read the article

-   [#async](https://hashnode.com/tag/async)
-   [#python](https://hashnode.com/tag/python)
-   [#threading](https://hashnode.com/tag/threading)
-   [#event-loop](https://hashnode.com/tag/event-loop)

## Written by

[Danny Crasto](https://hashnode.com/@danwald)

@danwald · dubai, uae

  
[View profile](https://hashnode.com/@danwald)

backend/cloud engineer | mentor | pythonista

I am developer/code-reviewer/debugger/bug-fixer/architect/teacher/builder from dubai, uae

## Responses

Markdown supported · ⌘↵ to post

No responses yet.