►
From YouTube: Node.js Community Benchmarking WG Meeting
A
Hello,
welcome
to
the
nodejs
community,
bounded
benchmarking
workgroup
meeting
for
December
4th
2017
I
think
we're
gonna
have
a
fairly
short
small
meeting.
Today's
there's
only
myself
and
power,
but
we
might
as
well
go
through
our
agenda
anyway.
So
any
announcements
I
don't
have
any
this
week.
Utam
do
you
have
any.
A
B
Maybe
I
should
have
updated
the
the
issue,
but
there
is
it
perform.
There's
a
huge
performing
difference
between
the
zero
point,
one
one
which
was
the
previous
version
of
ghost
and
the
latest
release,
which
is
one
point.
Oh
and
the
difference
is
as
big
as
almost
30%
so
I
we
don't
want
to
add
a
workload
and
then,
if
someone
was
you
go
straight,
they
won't.
They
should
see
this
difference
and
that
would
be
very
confusing
yep,
so
I
think
we
would
like
to
get
some
I'll.
Let
me
update
the
issue.
A
I
just
took
a
notice
as
huge
difference
between
0.1,
1
and
1/4
almost
represents
the
room,
will
update
the
issue
and
take
back
to
get
up
to
be
discussed
next
meeting.
Ok
sounds
good
and
here
I'm
actually
gonna
share
my
screen
so
that
people
can
see
I
don't
want
to
share
all
my
screen
want
to
share
one
window.
There
you
go
so
people
in
okay.
Next
thing
on
the
agenda
was
survey.
A
Questions
for
end-users,
decide
what
the
benchmark
that's
was
discussed
in
in
the
end
user
feedback
meeting
late
last
week,
Friday
I
believe
and
the
outcome
is,
is
that
we
are
going
to
you
know:
we've
taken
the
questions.
There
was
some
discussion
around
whether
there
should
be
more
multiple-choice
and
stuff
like
that.
A
It's
gonna
be
sent
to
the
the
person
in
the
foundation
and
normally
puts
them
together
to
sort
of
put
together
a
draft
of
the
benchmarking
of
the
the
poll
to
go
out.
We're
gonna
have
meet
and
have
some
discussions,
and
the
goal
is
to
basically
review
and
do
the
final
sign-off
two
weeks
from
last
Friday
and
then
actually
you
know,
we
discussed
whether
it
was
good
sending
the
survey
out
over
the
the
Christmas
or
the
holiday
season.
The
feeling
was
well
actually
that
might
give
developers
more
time
to
think
about
it
and
stuff.
A
B
A
Okay,
next
one
is
status
of
running
the
note
core
or
benchmarks:
okay,
so
that
one
I
know
that.
A
A
A
B
A
Okay,
so
let's
just
see,
if
there's
any
interesting
discussion
there,
okay,
I
guess
there
was
one
issue
reported
in
terms
of
its
usage
that
is
related
to
getting
some
extra
pieces
installed,
but
that
seems
like
about
it.
There
is
about
eight
people
who
sort
of
thumbed
up,
so
at
least
we
got
some
visibility.
I,
don't
think,
there's
anything
else
to
discuss
on
that
front.
B
So
is
this
going
to
be
added,
as
in
people
done
all
this
API
is
the
buffer
and
the
streams
and
the
string
decoders
alright.
A
A
Well,
no
anyway,
but
Benedict
had
asked
somebody
to
look
at
building
like
looking
at
the
mall
and
trying
to
come
up
with
a
smaller
set,
which
would
make
sense
and
to
run
regularly.
So
that's
still
under
way.
This
is
sort
of
independent
of
that
it
basically
you
know,
gives
a
you
know
a
tool
people
can
use
and
if
we
can
make
it
better
and
run
things
at
night
at
some
point,
that'd
be
good,
but
this
is
a
good
first
step.
A
A
A
A
B
A
Could
add
something
it's
kind
of
like
we
should
do
this
in
ansible,
but
we
haven't
started
yet
like
if
we
already
had
the
scripts
would
be
simple
right.
What
you
think.
B
A
A
B
A
B
A
A
Okay,
so
I
think
that's
about
it
for
this
week.
That
will
just
give
people
a
chance
for
Q&A.
So
if
anybody
has
a
question,
you
can
add
it
into
the
original
issue
itself,
we'll
just
give
you
a
minute
or
two
to
do
that,
while
that's
happening
I
think
we
should
talk
about
next.
The
next
meeting,
so
calendar
I'm,
just
gonna,
go
check
to
see.
The
next
meeting
is
scheduled
for
two
weeks
from
now
I'm
on.