|
| 1 | + |
| 2 | + |
1 | 3 |
|
2 | 4 | [](https://codecov.io/gh/redis/redis-benchmarks-specification)
|
3 | 5 | [](https://github.com/redis/redis-benchmarks-specification/actions/workflows/tox.yml)
|
4 | 6 | [](https://pypi.org/project/redis-benchmarks-specification)
|
5 | 7 |
|
| 8 | + |
6 | 9 | ## Installation
|
7 | 10 |
|
8 | 11 | To have access to the latest SPEC and Tooling impletamtion you only need to install one python package.
|
@@ -58,63 +61,7 @@ python3 -m pip install redis-benchmarks-specification
|
58 | 61 |
|
59 | 62 | ## Architecture diagram
|
60 | 63 |
|
61 |
| -``` |
62 |
| - |
63 |
| - |
64 |
| -┌──────────────────────────────────────┐ |
65 |
| -│1) gh.com/redis/redis update │ |
66 |
| -│ - git_repo: github.com/redis/redis │ |
67 |
| -│ - git_hash: 459c3a │ |
68 |
| -│ - git_branch: unstable │ |
69 |
| -└─────────────────┬────────────────────┘ |
70 |
| - │ |
71 |
| - │ ┌───────────────────────────────────┐ |
72 |
| - │ │HTTP POST │ |
73 |
| - └──────┤<domain>/api/gh/redis/redis/commit │──┐ |
74 |
| - └───────────────────────────────────┘ │ |
75 |
| - │ |
76 |
| - ▼ |
77 |
| - ┌──────────────────────────────────────────┐ |
78 |
| - │2) api │ |
79 |
| - │ - Converts the HTTP info into an stream │ |
80 |
| - │entry │ |
81 |
| - │ - XADD stream:redis:redis:commit <...> │ |
82 |
| - │ │ |
83 |
| - └─────────────────────┬────────────────────┘ |
84 |
| - │ |
85 |
| - │ |
86 |
| - │ |
87 |
| - │ ┌────┐ |
88 |
| - .─────────────────────────────────────. │ │push│ |
89 |
| - ┌─────┐ ┌ ▶( 2.1 ) stream of build events )◀───┘ └────┘ |
90 |
| - │pull │ `─────────────────────────────────────' |
91 |
| - └─────┘ │ |
92 |
| - |
93 |
| - │ ┌────────────────────────────────────────────┐ |
94 |
| - ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─│2.2) build_agent │ |
95 |
| - │ - based on setup platforms │ |
96 |
| - │ - build different required redis │ |
97 |
| - │artifacts │ |
98 |
| - └───────────────────────┬────────────────────┘ |
99 |
| - │ |
100 |
| - │ |
101 |
| - │ ┌────┐ |
102 |
| - .─────────────────────────────────────. │ │push│ |
103 |
| - ┌─────┐ ─▶( 2.3 ) stream of artifact benchmarks )◀────┘ └────┘ |
104 |
| - │pull ││ `─────────────────────────────────────' |
105 |
| - └─────┘ |
106 |
| - │ |
107 |
| - ┌────────────────────────────────────────────┐ |
108 |
| - │ │ │ |
109 |
| - │3) benchmark_coordinator │ |
110 |
| - │ │ - based on test-suites and setups: │ |
111 |
| - │ - Trigger env setup │ |
112 |
| - └ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─│ - 3.1 ) Trigger topology setup │ |
113 |
| - │ - 3.2 ) Run benchmarks │ |
114 |
| - │ - Record results into datasinks │ |
115 |
| - │ │ |
116 |
| - └────────────────────────────────────────────┘ |
117 |
| -``` |
| 64 | + |
118 | 65 |
|
119 | 66 | In a very brief description, github.com/redis/redis upstream changes trigger an HTTP API call containing the
|
120 | 67 | relevant git information.
|
|
0 commit comments