summaryrefslogtreecommitdiff
path: root/getting-started.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2017-12-03 18:32:14 +0200
committerLars Wirzenius <liw@liw.fi>2017-12-03 18:32:14 +0200
commitab6543dff85a5cd1a393e1eb003d265d5fbb8154 (patch)
treea3dd48961f430c91d69dccf846ae5a8af9cc0c3e /getting-started.mdwn
parent321c46a76f76a700c96e8efc0c9b1a3b21b91f25 (diff)
downloadick.liw.fi-ab6543dff85a5cd1a393e1eb003d265d5fbb8154.tar.gz
Add: quantify "very large number"
Diffstat (limited to 'getting-started.mdwn')
-rw-r--r--getting-started.mdwn3
1 files changed, 2 insertions, 1 deletions
diff --git a/getting-started.mdwn b/getting-started.mdwn
index 9f7343b..d4e4724 100644
--- a/getting-started.mdwn
+++ b/getting-started.mdwn
@@ -21,7 +21,8 @@ You probably want to start with these kinds of things.
* If you have access to the hardware, do some ick stress testing. Set
up an ick server with a very large number of workers, a very large
number of projects to build, and see if ick can handle that. Report
- the problems.
+ the problems. The unofficial wish is for Ick to handle 1000 worker
+ nodes building 1000 project concurrently.
Documentation things