At MapR (mostly unrelated to asterix), we deployed a system readiness test that is intended to be run before installing our system.
The point is to set expectations. If a simple test says that your hardware or network is deficient or severely misconfigured even before the real software is installed, users are less likely to expect miracles. See https://github.com/jbenninghoff/cluster-validation On Sun, Dec 16, 2018 at 3:54 PM Ian Maxon <[email protected]> wrote: > What should we fix? The one thing I can think of that is a bit > out-dated is the page size, and perhaps the # of nodes could be > configured automatically depending on the number of hardware threads > and disk type. However that still wouldn't prevent people from blindly > testing without thinking carefully about the configuration. Perhaps > some sort of limitation that is added in the demo config to stop > benchmarking but still allow simple use/evaluation , so it forces one > to look at the documentation to discover how to remove it (and hence > at least view the other config parameters)? > > On Sun, Dec 16, 2018 at 8:58 PM Michael J. Carey <[email protected]> > wrote: > > > > Naive users are routinely ending up with multiple node demo clusters and > > not realizing what they are doing or getting. Then they performance test > > and judge the system accordingly. Not beneficial! >
