2022-02-02 16:13:08 +01:00
# Usage:
This is an example demonstrating the construction of async state with `App::data_factory`
2020-06-22 15:16:25 +02:00
## Reason:
2022-02-02 16:13:08 +01:00
Use of a `data_factory` would make sense in these situations:
- When async state does not necessarily have to be shared between workers/threads.
2020-06-22 15:16:25 +02:00
2022-02-02 16:13:08 +01:00
- When an async state would spawn tasks on `actix-rt` . If state was centralized there could be a possibility the tasks get an unbalanced distribution on the workers/threads
2020-06-22 15:16:25 +02:00
(`actix-rt` would spawn tasks on local thread whenever it's called)
## Requirement:
2022-02-02 16:13:08 +01:00
- `rustc 1.58 stable`
2020-06-28 00:15:34 +02:00
- `redis` server listen on `127.0.0.1:6379` (or use `REDIS_URL` env argument when starting the example)
2020-06-22 15:16:25 +02:00
## Endpoints:
- use a work load generator(e.g wrk) to benchmark the end points:
http://127.0.0.1:8080/pool prebuilt shared redis pool
http://127.0.0.1:8080/pool2 data_factory redis pool
## Context:
The real world difference can be vary by the work you are doing but in general it's a good idea to
spread your *identical* async tasks evenly between threads and have as little cross threads synchronization as possible.