mirror of
https://github.com/wassname/ray.git
synced 2026-08-14 12:40:23 +08:00
Replace special single quote with regular single quote. (#1693)
This commit is contained in:
committed by
Devin Petersohn
parent
40799fee37
commit
cae108d019
@@ -112,7 +112,7 @@ with the Plasma store via messages serialized using [Google Flatbuffers][4].
|
||||
|
||||
Plasma is a work in progress, and the API is currently unstable. Today Plasma is
|
||||
primarily used in [Ray][2] as an in-memory cache for Arrow serialized objects.
|
||||
We are looking for a broader set of use cases to help refine Plasma’s API. In
|
||||
We are looking for a broader set of use cases to help refine Plasma's API. In
|
||||
addition, we are looking for contributions in a variety of areas including
|
||||
improving performance and building other language bindings. Please let us know
|
||||
if you are interested in getting involved with the project.
|
||||
|
||||
@@ -58,19 +58,19 @@ objects to and from the Arrow format. Some properties of this approach:
|
||||
reading the full object (requirements 1 and 4).
|
||||
- Arrow supports **zero-copy reads**, so objects can naturally be stored in
|
||||
shared memory and used by multiple processes (requirements 1 and 3).
|
||||
- We can naturally fall back to pickle for anything we can’t handle well
|
||||
- We can naturally fall back to pickle for anything we can't handle well
|
||||
(requirement 2).
|
||||
|
||||
**Alternatives to Arrow:** We could have built on top of
|
||||
[**Protocol Buffers**][5], but protocol buffers really isn't designed for
|
||||
numerical data, and that approach wouldn’t satisfy 1, 3, or 4. Building on top
|
||||
numerical data, and that approach wouldn't satisfy 1, 3, or 4. Building on top
|
||||
of [**Flatbuffers**][6] actually could be made to work, but it would have
|
||||
required implementing a lot of the facilities that Arrow already has and we
|
||||
preferred a columnar data layout more optimized for big data.
|
||||
|
||||
## Speedups
|
||||
|
||||
Here we show some performance improvements over Python’s pickle module. The
|
||||
Here we show some performance improvements over Python's pickle module. The
|
||||
experiments were done using `pickle.HIGHEST_PROTOCOL`. Code for generating these
|
||||
plots is included at the end of the post.
|
||||
|
||||
|
||||
@@ -96,9 +96,9 @@ cd ray/python/ray/rllib
|
||||
## Distributed Actor Handles
|
||||
|
||||
Ray 0.3 adds support for [distributed actor handles][1], that is, the ability to
|
||||
have multiple callers invoke methods on the same actor. The actor’s creator may
|
||||
have multiple callers invoke methods on the same actor. The actor's creator may
|
||||
pass the actor handle as an argument to other tasks or to other actor methods.
|
||||
Here’s an example in which the driver creates an actor to log messages and
|
||||
Here's an example in which the driver creates an actor to log messages and
|
||||
passes an actor handle to other tasks:
|
||||
|
||||
```python
|
||||
|
||||
Reference in New Issue
Block a user