►
From YouTube: Mina Community Node Working Group | Meeting 02.22.2022
Description
The weekly Node Working Group session serves as a platform for the community, ecosystem partners, and the Mina Foundation to interact.
This meeting is a time to discuss the latest core protocol releases and for members to propose suggestions, raise issues, and provide and get feedback.
If any community members have questions or feedback on the latest 1.3.0 beta 4 release, please visit the #mainnet-block-producers or #DevNet channel on the Mina Discord: https://bit.ly/MinaDiscord
Issues discussed can be found on GitHub: https://bit.ly/NWG-issues
Chapters
0:00 — Preamble
0:33 — Intro
1:27 — O(1) Labs GitHub issues updates and overview
5:18 — Quick Sync Times
7:15 — Improvements
10:30 — GraphQL API Request
13:30 — Seed Nodes
15:15 — How to leave feedback on the newest beta release
A
Here's
the
preamble,
the
noteworking
group
sessions
are
a
time
when
members
come
together
to
discuss
and
collaborate
with
ecosystem
partners
in
the
mina
foundation.
Topics
discussed
generally
include
latest
releases,
note
operations
and
other
technical
matters
related
to
the
protocol.
Although
this
is
the
discretion
of
the
node
working
group,
my
name
is
john
robinson:
I'm
the
community
operation
manager
of
the
mina
foundation
and
I'm
here
to
support
and
facilitate
these
sessions.
A
If
anyone
has
any
questions
during
a
meeting,
you
can
raise
your
hand.
We
have
a
very
small
meeting
today,
so
just
yeah
feel
free
to
talk.
This
meeting
will
be
recorded
and
we'll
post
it
on
youtube
and
it's
in
an
effort
to
increase
our
transparency
and
and
get
more
information
out
to
the
community
on
what
our
partners
and
people
are
working
on
thanks
everyone
for
adding
the
topics
to
the
agenda.
A
B
B
Many
of
those
changes
went
out
in
the
beta
last
week
and
we're
working
on
some
additional
changes
to
rosetta
and
the
archive
node
schema
that
are
going
to
affect
a
small
portion
of
the
user
base,
but
we
want
to
make
sure
those
are
all
included
for
1.3.0
stable
as
well,
and
we
will
be
working
this
week
to
get
to
that
to
reach
that
milestone
and
graduate
it
stable.
I
would
love
to
hear
any
feedback
either
now
or
or
in
the
future.
Anyone
seeing
this
on
youtube.
You
know
coming
to
the
discord.
A
A
B
I
think
those
are
the
big
things
besides
yeah
besides,
just
like
the
1.3
releases
in
general,
which
are
doing
things
like
getting
rid
of
old
coda,
underscore
naming
for
things,
and
just
just
that
sort
of
cleanup
and
and
code
structure,
improvements
that
are
making
it
a
lot
easier
to
make.
These
changes
and
to
make
improvements
going
forward.
A
Yeah
thanks
bender
one
thing
that
really
surprised
me
and
I
was
wondering
I
haven't
noticed
before,
but
it
was
really
fast
to
sync.
I
I'm
running
one
of
the
nodes
on
my
computer
at
home,
not
on
the
server
and
that
and
when
I,
when
I
start
that
up
again
I
mean
it
was
really
fast
to
sync
like
five
six
minutes.
So
that's
quite
a
big
change.
D
B
Yeah,
the
I
will
say
bootstrap
is
still
like
five
to
ten
minutes
and
depending
on
whether
or
not
you
have
local
disk
on
disk
state,
there's
another
process
that
it
has
to
do
to
sort
of
load
in
all
of
that
old,
persistent
storage
and
then
resolve
it
against
the
network.
So
there's
still
like
many
different
ways
that
you
can
that
that
first
bootstrap
period
actually
executes
and
some
of
them
are
faster
than
others.
B
I
think
that's
a
big
part
of
the
reason
why
you're
going
to
see
differences,
but
I
also
think
that
in
this
current
version
it
is
the
most
efficient
it's
ever
been,
so
ketchup
and
bootstrap
should
be
yeah
should
be
faster
than
they
have
been
for
you
in
the
past
and
really
under
all
of
those
conditions.
It
should
be
better
and
then
some
more
than
others
and
nathan.
Do
you
want
to
speak
more
on
that
and
more
on?
E
Yeah,
I
can
speak
a
little
bit
so
yeah
from
my
measurements.
I've
been
noticing
that
bootstrap
from
a
persistent
state
takes
about
five
to
ten
minutes
now
and
bootstrap
from
no
state
takes
about
20
to
25
minutes
on
average.
So
I'd
always
be
curious
in
hearing
if
that
matches
up
with
what
the
community
is
observing,
but
as
far
as
what
the
changes
were
that
help
with
this.
It's
really
what
andrew
was
talking
about
before,
with
especially
with
the
super
ketchup
optimization.
E
There
was
an
inefficiency
that
was
tracked
down
in
super
ketchup
that
what
we
didn't
find
when
we
first
introduced
super
ketchup,
because
it's
an
inefficiency
that
only
showed
up
as
we
had
more
catch-up
jobs
in
progress,
and
so
as
we
started
getting
more
ketchup,
jobs
and
progress,
and
the
network
started
like
seeing
increased
load
of
traffic.
This
started
becoming
a
big
issue
and
it
sort
of
has
like
a
exponential
effect
in
how
it
surfaced
itself.
E
So
we
track
that
down
and
fix
that,
and
we
expect
that
to
have
a
really
big
overall
improvement
to
how
many
resources
it
takes
like
how
quickly
it
takes
to
actually
do
your
initial
catch
up
after
you
finish,
bootstrapping,
but
also
the
overall
resources
consumed
by
ketchup
jobs
in
general,
as
you're
participating
in
the
chain.
So
really
hoping.
E
This
will
have
a
very
large
effect
on
the
damon's
performance
and,
in
particular,
I've
been
seeing
much
lower
cpu
utilization
of
the
daemon
while
participating
once
initial
ketchup
is
finished,
which
is
much
better
than
what
it
was
before,
where
we
would
typically
be
pegged
to
close
to
100
cpu
a
lot
of
times.
So
it
does
seem
to
be
significant
reduction
in
resource
usage.
B
These
things
were
contributing
to
some
of
the
performance
degradation
that
we've
been
seeing
when
nodes
run
for
really
long
periods
of
time,
because
the
amount
of
time
that
it
spends
busy
waiting,
I
think,
increases
over
as
the
node
continues
to
run
and
continues
to
run
more
catch-up
jobs
and
continues
to
just
be
in
a
steady
state
for
a
long
time
and
so
yeah
fixing
all
these
things
and
getting
the
cpu
and
ram
usage
spent
on
the
key
operations
to
keeping
the
node
alive
should
also
help
them
stay
alive.
Longer.
D
D
E
E
These
optimizations
we'll
have
to
do
more
research
into
and
properly
measure
on
our
end
before
we'll
know
for
sure,
but
I
think
it's
definitely
worth
a
shot
just
on
your
end,
to
with
the
new
release,
try
and
run
a
script
against
graphql
and
see
how
quickly
it
responds
and
how
reliable
it
is,
because
I
I
do
expect
definitely
some
performance
improvements
there.
You
know
not
being
pegged
at
100
cpu
all
the
time.
It
does
a
lot
for
the
damage
ability
to
respond
to
different.
E
And
to
that
point
I
think
that
I
haven't
been
testing
specifically
graphql,
but
we
ran
a
seed
node
for
about
a
week
now
with
these
changes
applied
and
that
node
has
not
seen
any
significant
performance
degradation
over
the
course
of
that
week.
So
I
think
that's
a
really
good
indicator
that
we're
headed
in
the
right
direction
here.
E
E
Oh
we're
not.
We
have
a
health
check
that
hits
every
now
and
again,
but
that's
not
what
I'm
measuring
I'm
measuring
overall
cpu
time
and
block
inclusion
time
so
just
how
it
performs
in
keeping
up
with
the
network.
I
have
not
set
up
a
script
that
measures
graphql
performance
along
with
that
at
the
moment.
B
Yeah,
but
we
are
also
hammering
the
health
checks,
are
hammering
graphql
we're
just
not
measuring
the
amount
of
time
that
each
request
takes,
but
our
nodes
do
do
serve
a
fair
bit
of
graphql
volume
as
a
result
of
the
way
that
we
deploy
them
so
yeah.
So
the
the
long
run
time
is
is
a
has
been
hard
to
achieve
on
our
seeds
for
exactly
these
same
reasons
that
you
all
are
experiencing
that
when
you
hammer
these
apis,
so
I
think
it's
a
good
sign.
B
There's
there's
becoming
more
and
more
scarce
reasons
to
to
like
need
to
to
downgrade,
and
really
we
don't
want
to
be
in
that
in
that
world
anymore.
We
want
to
be,
you
know,
building
better
and
better
software
with
every
release,
so
we're
looking
to
hit
that
bar
with
1.3,
and
we
will
be
recommending
exactly
that.
You
know
that
everyone
upgrade
and
and
move
all
your
infrastructure
over
and
sort
of
move
towards
the
new
world
of
what
we
can
do
with
mina.
A
A
A
A
All
right,
everyone
I'll
finish
the
recording
now
so.
Thank
you
very
much
thanks
a
lot
for
your
time.
Nathan
really
appreciate
it.
Andrew
always
appreciate
your
time
here,
it's
it's
really
great
and
it's
it's
really
good
to
see
all
the
changes
and
the
improvements
you're
making.
It's
really
appreciated.
I
mean
yeah
all
right,
everyone.
Thank
you
very
much
for
coming,
and
you
have
a
great
week.