Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Renat Idrisov
    @parsifal-47
    @dii14 I tried this image, was working for me :) do you still have this issue?
    according to dockerhub statistics it was pulled 9 times, so it should be possible
    feel free to create issue anyway
    dii14
    @dii14
    is the ridrisov/mzbench image supposed to support git?
    Renat Idrisov
    @parsifal-47
    not necessary, since it uses rpm with pre-compiled workers, the most probably not, you may find Dockerfile for this image here: https://github.com/machinezone/mzbench/blob/master/docker/Dockerfile it has git if centos7 has it
    dii14
    @dii14
    Hi
    I can see that while running a benchmark in the scenario tab there is this functionality which seems like it allows to send some command to some percentage of the worker nodes
    this seems really cool to me, but what kind of commands can I send?
    Timofey Barmin
    @timofey-barmin
    Hi, dii14
    you can call worker functions there
    dii14
    @dii14
    I tried calling wait and it failed
    Renat Idrisov
    @parsifal-47
    @dii14 what message did you get? "command execution failed"?
    dii14
    @dii14
    On screen message was "command failed"
    in the system logs I get the error:07:02:10.352 [error] <0.224.0> Command run failed with reason {badmatch,{[{'mzb_director16_0@127.0.0.1',[]},{'mzb_worker16_1@127.0.0.1',[ok,ok]}],[]}}
    Command:<<"wait()">>
    Stacktrace:[{mzb_director,handle_call,3,[{file,"/home/ridrisov/mzbench/node/_build/default/deps/mzbench/src/mzb_director.erl"},{line,110}]},{gen_server,try_handle_call,4,[{file,"gen_server.erl"},{line,629}]},{gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,661}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]
    My wait was empty but that's not the point, I get the same for a correct command:07:03:45.749 [error] <0.224.0> Command run failed with reason {badmatch,{[{'mzb_director16_0@127.0.0.1',[]},{'mzb_worker16_1@127.0.0.1',[ok,ok]}],[]}}
    Command:<<"wait(3 sec)">>
    Stacktrace:[{mzb_director,handle_call,3,[{file,"/home/ridrisov/mzbench/node/_build/default/deps/mzbench/src/mzb_director.erl"},{line,110}]},{gen_server,try_handle_call,4,[{file,"gen_server.erl"},{line,629}]},{gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,661}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]
    Renat Idrisov
    @parsifal-47
    I have reproduced your issue, sorry, the problem was in result code control, fixed now, please update master and try again, thanks for reporting this!
    dii14
    @dii14
    ok cool will try again
    dii14
    @dii14
    Actually I was never able to build from sources behind my proxy
    It is something to do with rebar3 fetching the "registry" package, I suspect that my variables for proxies are not read by rebar3
    dii14
    @dii14
    Do you know of any known problems with rebar3 and proxies?
    I saw a few issues online but they seem resolved
    Renat Idrisov
    @parsifal-47
    yes, I had an experience using rebar with proxy, but couldn't remember how exactly was it, but it worked, I found some website suggesting to set {http_proxy, "http://proxy.my-company.com:123"}. {https_proxy, "https://proxy.my-company.com:456"}. in rebar.config
    or alternatively, it could be env-variable http_proxy or HTTP_PROXY
    some of these should work :)
    dii14
    @dii14
    Hi there again
    Is there any way of specifying some env variable that will be available across all benchmarks?
    For example I have a list of hosts to which I need my clients to connect, so what I'm doing now is I copy paste the list into the editor every time. I would like to have a way to programatically change the variable every time the hosts change.
    dii14
    @dii14
    I was looking at the mzbench change_env functionality but that's only for a specific benchmark
    I would like to do this for all benchmarks
    Renat Idrisov
    @parsifal-47
    Hi, change_env has meaning for benchmarks in progress, currently there is no method to set "variables by default across all benchmarks", but you could set it at the beginning of each scenario with https://github.com/machinezone/mzbench/blob/master/doc/scenarios/spec.md#defaults
    and also we have some system variables set by mzbench itself, they are kind of global, but I'm not sure if that what you need
    Adrian Lewis
    @aidylewis
    Asked for us to hire an Erlang contractor to help you with this instead of paying 100K plus for a tool. May be ignored. I will look into this tool after an some IPv4 v IPv6 comparisons I am currently working on. Know some Erlang, but forgotten most of it. I thought Erlang was a beautiful construct and perfect for a load tool.
    Andre Rocha
    @sonecabr
    hey guys..sorry for my noobie doubt...so..I'm not a erlang developer and I expend some time to try pass the Authorization header with http worker or http_simple_worker...may you have some article or example to help me? I used the dls, not erl to write the scenario
    Renat Idrisov
    @parsifal-47
    no problem, started conversation in "issue"
    Urjit Singh Bhatia
    @urjitbhatia
    Hi folks. I've been trying to run some tests on EC2. I have a little confusion: when I say: pool size 1000 and start 2 nodes does it mean I am actually running 500 workers each or 2000 total?
    Timofey Barmin
    @timofey-barmin
    500 workers each
    Urjit Singh Bhatia
    @urjitbhatia
    awesome! thanks for the answer :thumbsup:
    what is the recommended max workers per node for EC2? say c4.large instances
    running 5000 total on 2 nodes caused pool crashes
    (using the recommended AMIs)
    Timofey Barmin
    @timofey-barmin
    I would say it depends on your worker and worker script
    Urjit Singh Bhatia
    @urjitbhatia
    hmm, I am using the vernemq mqtt load testing script
    the funny thing is that CPU, Memory etc on the nodes looked healthy
    Timofey Barmin
    @timofey-barmin
    it should not crash
    Urjit Singh Bhatia
    @urjitbhatia
    is there any documentation about how many ports I can open for the default AMIs etc? I guess I need to do some more test runs and tweak the nodes themselves
    does this point anywhere? exit with reason reached_max_restart_intensity in context shutdown ?
    Renat Idrisov
    @parsifal-47
    it depends on your linux settings, could be checked with
    echo /proc/sys/net/ipv4/ip_local_port_range
    more information on this: