make number of workers default to number of available cpus about carbon-c-relay HOT 6 CLOSED

-w allows you to multi-thread more or less, if you don't see huge amounts of cpu being taken, you can leave it alone. On larger machines, you may want to increase the value to e.g. the number of available cpu cores.
-b specifies how many metrics are sent to a server at once at most, some receivers really choke when they get a large batch of metrics at once, and would need decreasing this value. The larger the batch, the more efficient the sending gets.
-q the number of metrics that can be enqueued for sending to the server. The bigger this value, the longer the relay can hold up metrics when the server can't handle, or is down, but also the more memory the relay will consume.

from carbon-c-relay.

-w would you consider making an auto setting that uses # of cores?
-t Can this be used to test rewrite rules?

from carbon-c-relay.

-w: yeah, there's just no uniform way to do it, needs some platform specific work, which I was trying to avoid
-t: exactly

from carbon-c-relay.

-w no worries, -w $(grep -c processor /proc/cpuinfo) works well enough :D
-t how exactly? I have about 20 rules and would like the ability to see which rule(s) a metric hits

from carbon-c-relay.

nproc should do the job as well

when run with -t just type the metrics in the console, for instance:

bla.foo.bar 
aggregation
    ^(bla.*)$ (regex) -> bla.foo.bar
    sum(\1_sum) -> bla.foo.bar_sum 
foo.bar
nothing matched foo.bar

from carbon-c-relay.

Well thanks for getting back to me so quickly. Not sure what I was doing wrong but got it working. thanks again.

from carbon-c-relay.