►
From YouTube: Node.js Benchmarking WG Meeting 2019-11-12
Description
A
Okay
and
my
understanding
is
that
when
it
says
preparing
to
livestream
the
seminar
it's
already
actually
live,
so
so
welcome
everybody
to
the
OGS
benchmarking
team
meeting
for
November
12
2019.
We
probably
going
to
have
a
short
agenda
today
and
an
informal
one
at
that.
The
one
item
that
is
coming
up
that
we
have
kind
of
thought
about
talking
about
is
the
benchmarking
survey
and
let
me
just
try
and
get
that
shared
here.
Oh
this
is
zoom.
Okay,
let
me
start
the
Google
Chrome
here
there
we
go.
A
C
A
A
B
A
A
B
A
Basically,
yeah
and
and
not
only
not
only
whether
they
have
used
it
at
all,
but
how
much
they
have
used
it
so,
for
example,
so,
for
example,
the
the
deep
equal
buffer
thing,
they've
they've,
used
it
for
for
a
better
part
of
a
year
right
so
so
to
two
of
the
six
people
who
have
responded
here
have
used
it
for
the
better
part
of
a
year.
So
that's
that's
a
fairly
strong
indication
right,
whereas,
whereas
you
know
a
purple,
isn't
as
strong,
you
know
that
kind
of
thing.
So.
D
A
B
A
So
yeah
so
basically
the
red
ones,
the
red
ones
are
strong
indications
and-
and
so
you
know
and
I
think
yeah
I
guess
this
is
not
buffer
anymore.
This
is
yeah
deep,
equal
primitives
and
objects,
so
yeah,
so
they've
used
that
a
little
bit,
but
but
basically
these
are
these-
are
the
responses
and
I
just
wanted
to
run
these
by
you
and
and
I?
Don't
know:
do
you
guys
have
access
to
this
like
readwrite?
So
you
can
also
see
these.
B
A
A
A
Where
was
that
no
just
release
but
I'm
fairly
certain
that
I
echoed
this
in
the
quarry
boy.
I'd
have
to
find
the
I
have
to
find
the
comment
that
I
made
in
the
core
issues
or
the
koribo
issues
for
this,
but
so
all
the
collaborators
are
aware.
I
don't
know
who
specifically
answered
because
it
was
intentionally
made
to
be
an
anonymous
service.
D
D
A
B
A
Here's
here's
another
one
typical
typed
array,
so
there's
a
lot
of
deep
equal
going
on
here's
one,
that's
all
year,
long
for
the
better
part
of
a
year
all
year
long!
So
did
you
know?
Okay,
this
one
is
a
little
weaker,
but
for
base64
decode,
because
it's
only
for
a
couple
of
months,
so
this
one
may
not
be
that
relevant.
A
This
one
is
about
the
same.
Perhaps
even
less
basic
c4
isn't
isn't
gaining
much
traction,
so
then
buffer
bike
length
again
buffer
buffer
buffer.
Not
surprisingly,
this
one
is
a
little
weaker,
but
it
looks
like
buffer
is.
Is
I
mean,
not
surprisingly,
it's
fairly
popular
right,
so
this
one
is
concat
is
not
that
important
yeah.
B
A
B
B
A
B
Then
we
can
think
that
out,
let's
give
me
the
names
in
each
of
them
with
more
than
twenty
percent
or
something
like
that,
and
then
we
can
that's
the
list
we
can
start
with.
That
would
be
my
at
least
something
I
think
would
be
useful,
but
no,
it's
not
still
not
very
strong
I.
Imagine
that
we
have
supporting
so
many
features
but
they're
not
as
strong
as
I
imagined,
but
nevertheless,
if
it's
less
more
than
twenty
percent,
let's
pick
them
and
let's
start
with,
because
we
have
to
track
them
at
some
point
right.
Yeah.
A
B
A
Kind
of
get
like
a
popularity
going,
so
so
that's
okay,
that
that's
something
that
I
can
I
can
probably
do
for
next
time
and
then
and
then
just
copy
this
sheet
over
cuz
I.
Don't
think
it's
gonna
be
moving
much,
but
I
don't
want
to
I,
don't
want
to
jeopardize
it's
getting
out
of
sync
with
with
the
actual
responses,
because
there
may
be
some
Google
magic
behind
it.
You
know
like
there's
more
more
stuff
is
gonna
show
up
here,
right
and
I.
A
B
So
and
then
we
can
move
on
next
step.
We
can
take
once
we
apply
the
score.
We
can
take
this
small
now
filtered
list
with
some
filter
on
saying,
hey
more
than
20%
and
then
that's
something
we
can
begin
we'll,
send
it
out
to
various
groups.
Yeah
say
this
is
what
we
think
we
should
start
with,
because
this
is
out
the
response
was
and
then
okay.
A
D
Thank
you
for
the
question,
so
I
have
too
much
time
to
do
too
much
has
some
issues
that
we
are
trying
to
solve
them.
It's
related
to
moongoose.
You
would
like
to
update
that,
and
I
also
would
like
to
follow
up
on
all
the
issue
that
is
related
to
to
the
fact
that,
on
the
side,
we
do
not
see
all
the
node.js
versions
running
well
under
no
dcis,
so
that's
also
an
issue
that
should
should
be
the
go
to
it.
We
have
an
issue
open
for
this.
Okay.
B
A
Not
no
I
I
only
have
I
only
have
access
to
to
the
CI
and
only
to
start
jobs
so
but
I
mean
anybody
can
pretty
much
request
access
to
to
the
infrastructure
machines.
It's
just
you
know
you
have
to
go
through
the
proper
channels
like
you
can
find
like
an
issue.
I
think
a
good,
a
good
place
to
start
would
be
would
be
the
the
build
work
because
they
know
they
know
the
infrastructure
best.
B
Because
what
opportunity
skyping,
that
issue
nor
DCI
seems
to
be
having
problem
with
couple
of
load
builds,
for
example,
that
the
canary
build
or
master
build,
so
he
won't
sue
and
I
looked
at
log
file.
It
seems
to
be
some
old
issue,
so
if
it
is,
if
it
is
possible,
he
needs
to
go
and
kind
of
try
to
run
it
by
hand
using
that
particular
node
version
and
see
whether
the
issue
goes
away
or
reproducible,
and
there
might
be
some
orphan
process
from
long
time
running.
A
Yeah,
so
so
Octavian,
if
you
need,
if
you
need
infrastructure
access,
I,
think
I.
Think
if
you
opened
an
issue
on
on
nodejs,
slash,
build,
then
then-
and
you
explain
what
the
situation
is:
I'm
sure
that
I'm
sure
that
they'll
be
able
to
help
you
out
and
there's
there's
there's
also
an
IRC
channel
on
freenode
called
hash
hash
node
build
if
I
remember
correctly
and
all
the
build
folks
are
there.
So
so
you
can
ping
them
there
and
they
can
help
you
with
with
this.
Thank.
D
A
B
A
And
then
you
get
the
IP
of
the
machine
after
Dave
after
they've
added
your
your
public
key
you
and
then
you
you
can
log
into
the
machine
there.
You
get
a
username
and
with
your
public
key
you
you
log
in
and
then
you
poke
around
and
then,
when
you're
done
you
in
the
issue,
you
comments
that
you
are
done
using
your
public
key
and
that
they
please
remove
it,
and
so
what
they
do
then
is
they
remove
your
public
key
and
they
close
the
issue.