{"author":null,"author_email":null,"bugtrack_url":null,"classifiers":[],"description":"

Unified Distributed Execution

\n\n

\n\n### What is unidist?\n\nunidist is a framework that is intended to provide the unified API for distributed execution by supporting various performant execution backends. At the moment the following backends are supported under the hood:\n\n* [MPI](https://www.mpi-forum.org/)\n* [Dask Distributed](https://distributed.dask.org/en/latest/)\n* [Ray](https://docs.ray.io/en/master/index.html)\n* [Python Multiprocessing](https://docs.python.org/3/library/multiprocessing.html)\n\nunidist is designed to work in a [task-based parallel](https://en.wikipedia.org/wiki/Task_parallelism) model.\n\nAlso, the framework provides a Python Sequential backend (`pyseq`), that can be used for debugging.\n\n### Installation\n\n#### Using pip\n\nunidist can be installed with `pip` on Linux, Windows and MacOS:\n\n```bash\npip install unidist # Install unidist with dependencies for Python Multiprocessing and Python Sequential backends\n```\n\nunidist can also be used with MPI, Dask or Ray execution backend.\nIf you don't have MPI, Dask or Ray installed, you will need to install unidist with one of the targets:\n\n```bash\npip install unidist[all] # Install unidist with dependencies for all the backends\npip install unidist[mpi] # Install unidist with dependencies for MPI backend\npip install unidist[dask] # Install unidist with dependencies for Dask backend\npip install unidist[ray] # Install unidist with dependencies for Ray backend\n```\n\nunidist automatically detects which execution backends are installed and uses that for scheduling computation.\n\n**Note:** There are different MPI implementations, each of which can be used as a backend in unidist.\nMapping `unidist[mpi]` installs `mpi4py` package, which is just a Python wrapper for MPI.\nTo enable unidist on MPI execution you need to have a working MPI implementation and certain software installed beforehand.\nRefer to [Installation](https://mpi4py.readthedocs.io/en/latest/install.html) page of the `mpi4py` documentation for details.\nAlso, you can find some instructions on [MPI backend](https://unidist.readthedocs.io/en/latest/optimization_notes/mpi.html) page.\n\n#### Using conda\n\nFor installing unidist with dependencies for MPI and Dask execution backends into a conda environment\nthe following command should be used:\n\n```bash\nconda install unidist-mpi unidist-dask -c conda-forge\n```\n\nAll set of backends could be available in a conda environment by specifying:\n\n```bash\nconda install unidist-all -c conda-forge\n```\n\nor explicitly:\n\n```bash\nconda install unidist-mpi unidist-dask unidist-ray -c conda-forge\n```\n\n**Note:** There are different MPI implementations, each of which can be used as a backend in unidist.\nBy default, mapping `unidist-mpi` installs a default MPI implementation, which comes with `mpi4py` package and is ready to use.\nThe conda dependency solver decides on which MPI implementation is to be installed. If you want to use a specific version of MPI,\nyou can install the core dependencies for MPI backend and the specific version of MPI as `conda install unidist-mpi `\nas shown in the [Installation](https://mpi4py.readthedocs.io/en/latest/install.html)\npage of `mpi4py` documentation. That said, it is highly encouraged to use your own MPI binaries as stated in the\n[Using External MPI Libraries](https://conda-forge.org/docs/user/tipsandtricks.html#using-external-message-passing-interface-mpi-libraries)\nsection of the conda-forge documentation in order to get ultimate performance.\n\nFor more information refer to [Installation](https://unidist.readthedocs.io/en/latest/installation.html) section.\n\n#### Choosing an execution backend\n\nIf you want to choose a specific execution backend to run on,\nyou can set the environment variable `UNIDIST_BACKEND` and unidist will do computation with that backend:\n\n```bash\nexport UNIDIST_BACKEND=mpi # unidist will use MPI\nexport UNIDIST_BACKEND=dask # unidist will use Dask\nexport UNIDIST_BACKEND=ray # unidist will use Ray\n```\n\nThis can also be done within a notebook/interpreter before you initialize unidist:\n\n```python\nfrom unidist.config import Backend\n\nBackend.put(\"mpi\") # unidist will use MPI\nBackend.put(\"dask\") # unidist will use Dask\nBackend.put(\"ray\") # unidist will use Ray\n```\n\nIf you have installed all the execution backends and haven't specified any of the execution backends, MPI is used by default.\nCurrently, almost all MPI implementations require ``mpiexec`` command to be used when running an MPI program.\nIf you use a backend other than MPI, you run a program as a regular python script (see below).\n\n#### Usage\n\n```python\n# script.py\n\nimport unidist\nunidist.init() # MPI backend is used by default\n\n@unidist.remote\ndef foo(x):\n return x * x\n\n# This will run `foo` on a pool of workers in parallel;\n# `refs` will contain object references to actual data\nrefs = [foo.remote(i) for i in range(5)]\n# To get the data call `unidist.get(...)`\nprint(unidist.get(refs))\n```\n\nRun the `script.py` with:\n\n```bash\n$ mpiexec -n 1 python script.py # for MPI backend\n# $ python script.py # for any other supported backend\n[0, 1, 4, 9, 16] # output\n```\n\nFor more examples refer to [Getting Started](https://unidist.readthedocs.io/en/latest/getting_started.html) section\nin our documentation.\n\n### Powered by unidist\n\nunidist is meant to be used not only directly by users to get better performance in their workloads,\nbut also be a core component of other libraries to power those with the performant execution backends.\nRefer to `Libraries powered by unidist` section of [Using Unidist](https://unidist.readthedocs.io/en/latest/using_unidist/index.html) page\nto get more information on which libraries have already been using unidist.\n\n### Full Documentation\n\nVisit the complete documentation on readthedocs: https://unidist.readthedocs.io.\n","description_content_type":"text/markdown","docs_url":"https://pythonhosted.org/unidist/","download_url":null,"downloads":{"last_day":-1,"last_month":-1,"last_week":-1},"dynamic":null,"home_page":"https://github.com/modin-project/unidist","keywords":null,"license":"Apache-2.0","license_expression":null,"license_files":null,"maintainer":null,"maintainer_email":null,"name":"unidist","package_url":"https://pypi.org/project/unidist/","platform":null,"project_url":"https://pypi.org/project/unidist/","project_urls":{"Homepage":"https://github.com/modin-project/unidist"},"provides_extra":["all","dask","mpi","ray"],"release_url":"https://pypi.org/project/unidist/0.7.2/","requires_dist":["packaging","cloudpickle","ray[default]>=1.13.0; extra == \"all\"","pydantic<2; extra == \"all\"","dask[complete]>=2.22.0; extra == \"all\"","distributed>=2.22.0; extra == \"all\"","mpi4py>=3.0.3; extra == \"all\"","msgpack>=1.0.0; extra == \"all\"","psutil; extra == \"all\"","dask[complete]>=2.22.0; extra == \"dask\"","distributed>=2.22.0; extra == \"dask\"","mpi4py>=3.0.3; extra == \"mpi\"","msgpack>=1.0.0; extra == \"mpi\"","psutil; extra == \"mpi\"","ray[default]>=1.13.0; extra == \"ray\"","pydantic<2; extra == \"ray\""],"requires_python":">=3.9","summary":"Unified Distributed Execution","version":"0.7.2","yanked":false,"yanked_reason":null}

Dependency	Optional
cloudpickle	false
packaging	false
dask	true
distributed	true
mpi4py	true
msgpack	true
psutil	true
pydantic	true
ray	true

Package search

unidist

project_urls

Dependencies

All package metadata

Releases