Skip to content

Revise GIL section for Python 3.13 updates #742

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
timkofu wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Revise GIL section for Python 3.13 updates #742

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions docs/get_started.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,13 +236,14 @@ choice to create a pool of reusable worker threads.

.. attention::

`GIL <https://wiki.python.org/moin/GlobalInterpreterLock>`_ has the potential to
undermine your concurrency performance, as it prevents multiple threads from
accessing the same line of code simultaneously. Libraries like
`NumPy <http://www.numpy.org/>`_ can mitigate this for parallel intensive
computations as they free the GIL. RxPy may also minimize thread overlap to some
degree. Just be sure to test your application with concurrency and ensure there
is a performance gain.
The `GIL <https://wiki.python.org/moin/GlobalInterpreterLock>`_ has the potential to
undermine your concurrency performance in Python versions prior to 3.13, as it prevents
multiple threads from accessing the same line of code simultaneously. Starting with Python 3.13,
the GIL can be disabled via the free-threading mode (enabled with the `--disable-gil` build option),
allowing for true multi-threading parallelism. Libraries like `NumPy <http://www.numpy.org/>`_
can mitigate GIL limitations for parallel intensive computations as they release the GIL during
operations. RxPy may also minimize thread overlap to some degree. Just be sure to test your application
with concurrency and ensure there is a performance gain, especially when using free-threading builds.

The :func:`subscribe_on() <reactivex.operators.subscribe_on>` instructs the source
:class:`Observable <reactivex.Observable>` at the start of the chain which scheduler to
Expand Down