You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -252,7 +252,7 @@ You can see the spike in CPU and bandwidth on the droplet, but the CPU never sat
252
252
These are by no means comprehensive benchmarks but give you a sense of what a PCP server can withstand for simple use case.
253
253
Going above 400 req/s generally results in bad things happening. You can test your own site using [k6](https://k6.io/) with the instructions in [loadtest.js](./loadtest.js)
254
254
255
-
# Roadmap
255
+
# Roadmap & releases
256
256
257
257
## Release 0.0.1
258
258
-[x] Run arbitrary scripts
@@ -268,6 +268,10 @@ Going above 400 req/s generally results in bad things happening. You can test yo
268
268
-[x] Document PCP
269
269
-[x] Load test a production deployment
270
270
271
+
## Release 0.0.2
272
+
-[ ] Perfomance improvements
273
+
-[ ] Cluster mode
274
+
271
275
## Release 0.1.0
272
276
-[ ] Store passphrases with [konserve](https://github.com/replikativ/konserve)
273
277
-[ ] Add sponsorship button
@@ -285,6 +289,7 @@ For the guidance and examples, special thanks to
0 commit comments