Fork me on GitHub
#onyx
<
2017-08-06
>
a.espolov15:08:18

How many virtual onyx nodes can I create on a 4-core processor?

mike_ananev18:08:18

hi. have you ever considered to publish onyx as bundle to cloud platforms such as https://dcos.io ?

Travis18:08:10

@mike1452 I am not sure how that would work. Your tasks are bundled together as data with your deployed peers. I ran onyx on dcos by just deploying via marathon and scing

lucasbradstreet18:08:42

@a.espolov I’ve run up to 70+ on a 4 core box, but you need to tune some things, and it greatly depends on what your peers are doing.

lucasbradstreet18:08:38

@a.espolov you need to tune http://www.onyxplatform.org/docs/cheat-sheet/latest/#peer-config/:onyx.peer/idle-min-sleep-ns and http://www.onyxplatform.org/docs/cheat-sheet/latest/#peer-config/:onyx.peer/idle-max-sleep-ns to keep idle cpu burn low, "-Daeron.term.buffer.length=XXXX" to keep your buffers smaller so you don’t run out of shm space.

a.espolov20:08:05

@lucasbradstreet It is not difficult to give examples of the meaning of the listed parameters?

a.espolov20:08:32

idle-min-sleep-ns, idle-max-sleep-ns, -Daeron.term.buffer.length=XXXX

michaeldrogalis21:08:29

@a.espolov Some of these correspond directly to Aeron configuration opts. There’s more depth in their configuration manual - https://github.com/real-logic/aeron/wiki/Configuration-Options#common-options

lucasbradstreet22:08:52

The idle parameters are described in the links, but possibly the description should be improved. I've been meaning to document that Aeron option in the onyx docs but hadn't got around to it.

lucasbradstreet22:08:00

The idle parameters are the number of nanosecond that the peer will sleep if there is no work to be done. The greater the number, the less CPU burn while idle; though latency will increase accordingly.