diff --git a/docs/source/resource_control.rst b/docs/source/resource_control.rst index 78759836..46d96f01 100644 --- a/docs/source/resource_control.rst +++ b/docs/source/resource_control.rst @@ -22,9 +22,16 @@ Machine Resources Machine resources belong to certain "hardware" (or machine). Single machine can run multiple workers (usually through worker pools) -.. note:: +.. admonition:: Reminder + + | :ref:`Worker ` - is the component of Lifeblood that actually does the work + | **One** worker can do only **one** invocation job at the same time. + | Multiple workers can and are run on the same machine to efficiently use all available resources + | :ref:`Worker pool` is yet another component of Lifeblood responsible for managing workers on the same machine - + that's what you are actually launching on your machine(s) that you want to load with work. - :ref:`Worker ` - is the component of Lifeblood that actually does the work + Please note, Lifeblood's **Worker Pool** concept is **radically different from Deadline's concept of worker pools** + and means a completely different thing, so please don't think let a familiar word confuse you There are 2 fundamental types of machine resources: diff --git a/docs/source/usage.rst b/docs/source/usage.rst index de2dd440..64973e1c 100644 --- a/docs/source/usage.rst +++ b/docs/source/usage.rst @@ -171,8 +171,8 @@ Read more :ref:`in worker documentation ` .. _usage pools: -Use Pools instead -^^^^^^^^^^^^^^^^^ +Use Worker Pools instead +^^^^^^^^^^^^^^^^^^^^^^^^ Instead of starting individual workers you will probably want to start some kind of worker pool that will manage workers for you