►
From YouTube: Node.js Benchmarking WG Meeting
Description
A
It's
probably
cuz
chrome
crashed
on
me.
Let
me.
A
A
The
first
one
being
discussion
of
submissions
to
note
summit
Jess,
interactive,
EndNote
coffee.
You
just
thought
I'd
I
added
this
one
because
the
submission
season
is
on
and
if
we
want
to
submit
any
talks
related
to
benchmarking.
Now
is
probably
the
time
to
do
that.
Jess,
interactive
I
think
it
was
going
to
be
April
20th
that
it
was
closing,
but
it
may
have
been
extended,
neither
in
either
case.
We
still
have
time
on
on
all
three
of
them.
I
think.
C
A
It's
this
was
more
I,
don't
have
anything
specific
in
mind.
I
was
just
wondering
if
we
want
to
make
sure
that
we
got
something
on
the
benchmarking
front
up
and
submitted
I.
Guess
there
anything
that
we
have.
That
word
that
that's
interesting
enough,
that
we
think
we
want
to
be
like
putting
together
a
talk
on
I.
A
I
wasn't
I,
wasn't
you
know,
I
didn't
come
up
with
a
great
idea,
myself,
so
I
kind
of
agree,
unless
we
were
trying
to
you,
know,
get
some
public
public
like
just
trying
to
drum
up
interest,
but
I
think
we've
done
that
the
last
couple.
So
you
know,
unless
you
guys
have
good
ideas,
I'm
thinking,
maybe
this
time
we'll
leave
it,
as
is,
if
we
come
up
with
a
great
idea.
Well,
we'll
do
something.
Otherwise,
maybe
wait
till
next
time
and
hopefully
have
something
more
interesting
too.
B
A
A
The
next
one
is
footprint
increase.
I
think
we
touched
base
quickly
on
that
before
the
last
meeting,
so
I
think
there's
a
fix
coming
for
that.
We
just
need
to
kind
of
wait
for
that
to
come
through
the
cycle,
so
it
was
good
work
to
identify
the
issue
there
and
and
some
things
on
its
way.
That's
about
all
there
is
to
say
on
that
one
OH
require
perf
cache
much
lower
I.
Don't
think
anybody's
had
a
chance
to
take
a
look
at
that.
C
A
It
would
be
that
that,
basically,
if
you
require
something
that
was
already
required
before
it
makes
the
performance
of
that
decreased
significantly,
that's
pretty
bad
yeah
I
know
nobody's
let's.
Actually,
let's
open
the
here,
I'll
take
the
chart
and
Shh
I'll
try
and
share
we'll
see
what
happens
here.
My
machine
seems
to
be
a
little
unhappy
yeah.
A
C
C
A
B
A
B
A
A
B
A
A
A
B
A
A
B
Yeah
I'm
gonna
take
that
down.
I
was
just
finishing
up
with
another
actual
optimization
in
node
core
I
added
this
a
DP
DK
support,
which
accelerates
networking
stack
the
way
we
use
in
node.js
and
I'm
just
lost
via
phase
of
the
finishing
of
the
sanity
code,
sanity
and
sanitizing
the
code
for
the
comments,
adding
the
license
text
and
all
that
so
once
that
is
done,
hopefully
in
a
week
week
weeks
time
then
then
I'll
take
that
all
okay.
A
Sounds
good
okay,
so
that's
all
what
we
had
on
the
agenda.
A
I
guess
looping
back
to
the
earlier
discussion
about
times:
I,
wonder
if,
like
like.
Do
we
we've
been
scheduling
these
for
every
two
weeks,
I'm
wondering
if
if
we
need
them
every
two
weeks,
we've
missed
a
few
like
would
monthly
be
okay
or
I
mean
I,
don't
know
if
that
helps
or
makes
it
worse,
and
that
you
know
then
there's
let's
be
things
to
try
and
make
right,
but.
C
I
don't
know
I'm
whenever
I'm
trying
to
plan
this.
It
never
works
out
right,
it's
just
the
worst
time.
So
we
had
a
one
meeting
and
at
Google
at
this
time
that
I
had
to
attend
right
was
really
tough
to
make
it
I
had
to
be
on
site.
Even
okay,
I,
don't
know
when
I
went
it.
When
you
asked
me
now,
how
can
you
do
it
in
two
weeks
then
I
go.
Could
I
put
it
on
the
calendar?
Sure.
C
I
guess
yeah
it's
really
hard
to
find
the
time,
otherwise
that
works
for
you
guys.
Maybe
we
just
keep
it
like
this
and
I
will
try
to
make
it
and
if
not,
then
I
will
toss
on
the
my
updates
on
the
issue
later.
I
haven't
had
any
time
to
look
into
any
of
this
right
now,
so
I
want
to
set
up
the
promised
benchmarks.
Maybe
something
to
note
here
you,
you
erase
the
question
earlier
whether
we
should
have
been
benchmarks
for
promises
and
I
did
this
sweet
that
I
can
share
with
everyone.
D
I
know
I,
see
it
okay,
but
you
can
him
Utah
and
I
can
do
you
yeah
I?
Can
you.