If you look at https://asterixdb.apache.org/docs/0.9.4/ncservice.html,
which is prominently linked-to from the docs, what new users get is
information about "Starting a small single-machine cluster using the
NCService". This is of course a bad idea for any real usage - it is
only useful as a sample, so that AsterixDB explorers can play around
with a "cluster" on their laptops. Unfortunately, moderately intelligent
users have actually been known to declare this as the ""sterixDB default
configuration and then benchmark the system against it, using other
systems and their default configurations. We should have one CC and one
NC - and with spinning disks, one partition per device, and with SSD,
several partitions per device (determined by cores). I think it's A Bad
Thing that what one currently gets, if one's not thinking, is something
we wouldn't want anyone to ever really use.....
On 12/16/18 3:54 PM, Ian Maxon 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!
