►
From YouTube: Node.js Benchmarking Meeting 19 June 3PM
A
A
B
So
I
walked
on
a
proof
of
concept
to
capture
the
memory
trend.
Oh
and
I
mean
like
I.
Don't
have
it
like
something
to
show,
but
hopefully,
by
end
of
this
week,
I
should
have
like
I
will
try
to
use
the
same
scripts
that
we
use
Frightmare
or
memory
like
footprint,
recording
and
add
a
wrapper
to
it
to
capture
it
like
every
one.
B
Second
or
every
five
seconds,
whatever
and
and
just
like
calculate
the
area
like
just
sum
it
up
and
output
that
oh
that's
good,
yeah
other
than
that
I
was
playing
with
our
Jenkins
job
that
you
have
set
it
up.
Thanks
for
that
Oh
right
now,
the
know
to
recover
or
the
building
step
is
feeling
because
I
believe
the
Machine
doesn't
have
plan
compiler
yeah.
B
D
A
C
A
A
A
A
D
D
A
D
A
A
A
A
C
A
It's
basically
in
this
case,
like
deleting
the
seven
dot
X
in
the
XML
configuration
files,
so
yeah
you
can
put
together
a
PR
and
then
I
can
pretty
easily
test
it
in,
but
I
think
you'll
get
it
right.
Yet
the
other
thing
we
were
going
to
do
is
actually
change
the
colors,
so
it
ended
up
being
kind
of
an
ugly
color
for
eight.
So
if
you
can
change
the
color
from
what's
being
used
like
delete
seven
and
then
change
the
color
that
was
being
used
to
seven
to
what's
used
for
eight,
that
would
be
great.
A
Okay,
great
so
yeah
Kylie
take
a
look
at
that
better
great
okay
defy
jeaious
bench,
so
this
is
one
where
basically,
it
was
suggested
that
that
would
be
a
good
benchmark.
I,
don't
see
any
real
progress
on
that.
I'm
Bennett
mentioned
that
he
would
take
a
look
at
it,
but
that's
a
while
back,
maybe
I'll
ping
him.
A
Okay,
I
just
commented
I'll
not
exceed
depending
on
what
he
comes
back.
Maybe
one
of
the
rest
of
us
could
take
that
over.
If
it
doesn't
happen,
benchmark
data
cleanup,
this
one
is
still
active,
I
think
like
the
chart
to
getting
a
little
dense.
So
it's
basically
going
to
take
some
my
sequel
cleaning
again.
If
anybody
wanted
to
help
out
with
that,
I
could
get
them
a
copy
of
the
database
to
sort
of
test
it
offline,
and
then
we
could
run
it
on
the
actual
one.
Once
we
have
the
scripts
to
do
that,
so.
A
It's
my
sequel
database,
okay
and
the
schema
is
in
the
documentation
there
in
terms
of
you,
know
the
on
the
benchmark
in
the
repo
it
describes.
What's
in
there
I
think
you
know
what
we'd
want
to
do
is:
go
and
strip
out
like
every
I.
Don't
know
every
end
entry
so
that
it's
there's
just
not
quite
as
much
data
yeah.
You
know,
probably
spanning
the
same
period
of
time.
We
just
don't
need
quite
as
many
dots
and
we
might
even
think
about.
A
Can
we
trim
off
some
of
the
data
off
the
front,
whether
that
still
matters
or
not
so
probably
the
best
bet?
You
know
somebody
wanted
to
do
it
out,
so
we
should
do
it
outside
of
our
production.
You
know
the
production
of
our
met.
Just
I
could
provide
the
database,
install
my
sequel
and
then
play
with
the
scripts
that
would
clean
it
out
yeah
and
once
we
get
that
right,
just
apply
it
to
the
real
data.
B
A
H
D
A
Yeah
huge
area
start,
let
me
know
because
we
might
as
well
do
it
as
close
to
you
know,
not
I,
don't
want
to
go
grab
until
we're
actually
starting
to
work
on
it.
That's
all
I
know
DCE
is
to
the
benchmarks
week.
So
I
think
and
he'll
mention
they're
still
working
on
that
relevant
service
benchmarks.
I.
A
A
C
I
I
I
I
D
F
F
A
F
A
A
A
I
A
I
G
A
I
A
A
Unfortunately,
just
haven't
done
it
in
quite
a
long
time.
So
again,
that's
something
else.
Somebody
looked
at
the
charting
infrastructures
figured
out
how
to
add
in
you
know
a
good
way
to
add
in
the
dates,
probably
something
where
it
would
be.
You
know
we
want
another
config
file
that
like
had
the
dates
for
the
particular
releases
when
they
happened,
and
then
we
could
figure
out
how
to
sort
of
mark
those
on
the
charts
that
would
be
good
but
I'll
leave
it
open
for
somebody
to
grab
the
next
one
similar.
A
A
A
A
D
A
G
A
A
Think
that
one's
still
worth
leaving
open
as
well
until
we've
covered
over
our
matrix
and/or
covered
all
the
suggestions
in
here
which
we
haven't
done
yet.
So
that's
the
issues,
pull
requests
so
at
canola
and
Kyle
the
working
groups,
so
that
when
I
added
my
plus
one
I
see
Gareth
out,
it
is
his
as
well.
Actually
I
should
go
to
prove
so
we'll
just
let
that
sit
a
little
bit
and
if
there's
no
objections
and
we'll
move
forward.
D
A
E
A
A
B
A
Okay,
so
I
just
added
one.
This
is
good
all
the
follow-up
on
clang
issue
that
is
blocking
traffic
or
acne
runs.
You
know,
okay
and
then
our
next
meeting
is
scheduled
for
July
3rd
at
the
same
time,
yep
so
I
guess
unless
there's
something
else
we
have
to
discuss.
That's
it
for
this
week
sounds
good,
okay,
okay!
So
then
I
guess
we'll
talk
to
you
in
a
couple
weeks,
if
not
before
or
in
github.
Thanks
for
me,
yep
talk
to.