You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I think I remember a similar issue being opened about one of the other benchmarkers, but I can’t find it right now. Anyway, it would be nice to have h2load installed on the benchmarking machine so that we can run the HTTP/2 benchmarks there?
I'd be happy to take care of this, but I don't seem to have access to the machine (ssh root@50.23.85.254 -i /Users/jon/.ssh/nodejs_build_test isn't working.)
It's in the infra group. I've added the keys you have in GitHub onto the host so you can get in (maybe you should remove the one you don't need from there). Try to avoid the work if you see it working on any benchmarking tasks.
I do have an action to add keys specific to the benchmarking WG onto those machines but I have just never had time to get to it. I added a comment to #1147 so if we ever get around to the ansible scripts we don't forget to add to the list of ones that should be installed.
There are 3 benchmarking machines now, the original one and the 2 new ones from Intel. Its the 2 Intel ones that run the microbenchmarks job so we need to install on both of those.
@addaleax have you installed this before. I was looking to see if it as simple as installing with apt-get but all of the instructions I can find require building along with http2 and doing a full install of http2.
@mhdawson What I did locally was building directly from a https://github.com/nghttp2/nghttp2 checkout and installing it (maybe even manually cp’ed the h2load binary, not sure), that worked well enough for me
Activity
maclover7 commentedon Feb 25, 2018
I'd be happy to take care of this, but I don't seem to have access to the machine (
ssh root@50.23.85.254 -i /Users/jon/.ssh/nodejs_build_testisn't working.)cc @mhdawson @rvagg
rvagg commentedon Feb 26, 2018
It's in the infra group. I've added the keys you have in GitHub onto the host so you can get in (maybe you should remove the one you don't need from there). Try to avoid the work if you see it working on any benchmarking tasks.
mhdawson commentedon Feb 27, 2018
I do have an action to add keys specific to the benchmarking WG onto those machines but I have just never had time to get to it. I added a comment to #1147 so if we ever get around to the ansible scripts we don't forget to add to the list of ones that should be installed.
There are 3 benchmarking machines now, the original one and the 2 new ones from Intel. Its the 2 Intel ones that run the microbenchmarks job so we need to install on both of those.
addaleax commentedon Mar 6, 2018
Anything I can help with here? It would be nice to have the benchmarking machine available for nodejs/node#18936. :)
mhdawson commentedon Mar 6, 2018
@maclover7 you still planning to get to this ?
addaleax commentedon Apr 27, 2018
@nodejs/build Ping – this just came up for nodejs/node#20084, and I think it’s somewhat important… again, if I can help with something, let me know.
addaleax commentedon May 27, 2018
Hm … gentle ping @nodejs/build again :)
mhdawson commentedon May 28, 2018
@addaleax have you installed this before. I was looking to see if it as simple as installing with apt-get but all of the instructions I can find require building along with http2 and doing a full install of http2.
addaleax commentedon May 28, 2018
@mhdawson What I did locally was building directly from a https://github.com/nghttp2/nghttp2 checkout and installing it (maybe even manually
cp’ed theh2loadbinary, not sure), that worked well enough for memaclover7 commentedon May 28, 2018
Sorry for not getting back to this. This is already in progress via #1171, just haven't had time to get back to it. Will take a look now
ansible: add benchmarking