►
From YouTube: Node.js Benchmarking WG Meeting - July 31 2018
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Okay,
so,
first
of
all
the
first
issue
and
I'm
just
gonna
keep
an
eye
cause
I
think
it
has
been
trying
to
join.
We
just
can't
seem
to
promote
him
in
any
way
to
QuickLook
still
can
see
a
difference.
I'm
first
issue
on
the
list
is
membership
review.
So
this
is
number
230.
A
This
I
opened
just
to
suggest
that
we
should
do
a
membership
review.
I
think
that's
kind
of
good
practice.
We've
done
in
in
at
least
one
of
the
other
working
groups
just
to
sort
of
make
sure
we
have
that
the
list
that
we
list
on
our
readme-
it's
a
good
reflection
of
you-
know:
who's
involved,
who's
planning
to
be
involved
and
so
forth.
I
see
Gareth.
A
B
B
A
A
A
C
A
No
problem,
you
got
it
to
work,
that's
what
counts!
So,
just
we'll
quickly
flip
back
to
we're
discussion
that
discussing
the
membership
review,
I'm,
not
sure.
If
you've
taken
a
look
at
that
issue,
number
230
just
suggested.
We
do
a
review.
You
know
basically
posting
tasks
who
still
wants
to
be
active
in
the
working
group,
and
then
you
know
if
if
we
either
people
respond,
they're
not
going
to
be
active
or
don't
respond,
we'll
move
them
to
emeritus.
After
you
know
the
timelines
that
I've
suggested
that
sound
good
to
you
as
well.
Yeah.
C
A
A
C
A
C
C
D
D
C
A
D
A
So
it's
1
4
2
2
in
the
build
repo,
can
I
just
paste
it
into
the
bottom
of
that
issue.
So
yeah,
if
you
can
email
me,
your
SSH
keys,
just
the
you
know
the
public
key,
ok,
I'll,
add
them
to
the
authorized
keys
and
then
that'll
give
you
access.
Just
you
know,
obviously,
as
as
always
take
care
not
to
mess
up
the
existing
builds
or
anything
like
that.
But
probably
do
you
need
special
access,
or
is
it
ok
if
I
create
like
a
a
new
user
for
you,
I,
don't.
C
A
C
A
I'll
create
a
I'll,
create
a
user
specifically
for
you
with
your
own
home
directory
and
and
then
add
the
keys
there.
Ok,
okay
sounds
good
guess,
that's
it
on
that
issue
for
now,
so
we're
actually
I'm
sorry
I'm.
Just
getting
back
to
the
minutes
talk
where
is
that
it
goes
one
that
is
the
next
one.
I
just
want
to
take
a
minute,
a
few
minute
and
yeah.
A
few
notes,
though
one
before
I.
C
Yeah,
okay,
so
the
for
the
ghost
I
was
able
to
successfully
clone
the
ghost
and
able
to
set
up
on
a
machine.
The
way
should
be
running
on
node.js
benchmarking
said
any
problem:
I
disco
was,
it
does
not
work
with
mainline
at
the
master,
a
cat
just
worse,
with
the
released
six
and
eight
version
of
node.
Okay
and
another
thing:
what
I
learned
about
ghost
is
is
what
is
really
doing,
is
reading
a
database
and
just
creating
a
static
webpage.
Okay,
it
does
not
do
a
lot
of.
C
C
That
that
it
can
do
right,
which
are
actually
right
now,
the
Acme
ran
noticias
board,
does
lot
of
database
IO
in
and
only
thing
different
between.
Those
is
ghost
using
my
sequel
database,
but
carry
that
potentially
I
can
catch.
Okay
and
in
practical
terms,
ghost
is
normally
behind
run
behind
nginx
and
the
idea,
if
you
look
at
the
back
page,
be
the
maintainer
says
that
the
nginx
me
is
supposed
to
cache
those
web
pages
and
99%
will
not
hit
the
new
server
at
all
right.
D
A
A
C
Mostly
does
work
in
a
way,
but
so
it's
opposed
to
Moore's.
It's
oppose
the
development
mode
and
the
production
mode,
but
there's
a
huge
performance
gap
between
those
two
modes
right,
so
your
development
mode
will
work
with
our
load
master
branch,
but
it
will.
The
correction
will
not,
but
is
too
huge,
take
notes.
If
you
run
in
the
development
mode,
you
may
get
less
in
file
requests
per
second
versus
50
in
production
mode
right.
C
A
C
C
C
A
Mean
I
guess
I'd
lean
towards
if
it
doesn't,
if
it
doesn't
cover
something
significantly
different
than
those
other
two
I'd
lean
towards
saying.
Well,
maybe
it
doesn't
make
sense
after
all-
and
you
know,
I'd
rather
see
something
like
something
that
stresses
promises
get
in
or
something
like
that.
All.
C
D
D
A
A
C
A
C
A
A
D
C
A
A
C
A
C
C
Was
I
think
it
was
very
nice,
so
one
thing
I
noticed
was
I
was
talking
to
various
people
and
I
just
understand,
thinking
about
the
performance
and
a
lot
of
people
actually
did
not
know
about
our
benchmarking
got
no
jest
or
towards
it.
The
site
will
be
my
graphs,
so
I
had
to
literally
kind
of
show
you
to
few
people
where
they
can
go
over.
They
can
track
you
from
religious
and
when
they
only
switch
or
or
experiment
with
you.
Even
that
feedback
I
was
thinking
is
it?
A
D
A
C
A
And
we
can
do
that
a
bunch
of
different
ways.
So
if
you
know,
if
we
open
an
issue
which
is
more
generic,
which
is
like
better
promote
the
you
know
the
benchmark,
you
know
just
our
org
and
you
know
things
around
benchmarking.
One
of
the
things
we
can
do
is
is
try
and
get
the,
and
we
should
do
it
now,
because
there
is
that
work
on
the
the
website.
But
the
other
thing
too
is
we
could
get
the
the
the
like.
A
The
no
Deus
foundation
account
to
tweet
it
out
more
regularly
as
we're
doing
with
some
other
working
groups.
We
can
possibly
think
about,
like
you
know,
should
we
write
some
more
blogs
and
do
some
more
promotion
and
that
stuff,
because
I
think
that
that's
a
good
idea
in
that
you
know
we
could
use
some
more
fresh
faces
coming
in
and
and
more
people
looking
at.
What's
there,
okay,
I'll
open
issue,
okay,.