►
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
Hey
my
name
is
Gabe
Weaver
I'm,
the
acting
product
manager
for
the
application
performance
team,
joined
with
Alexi
who's,
a
senior
engineer
and
CZ
who's.
The
engineering
manager
for
the
team
we're
here
to
talk
about
our
15.7
kickoff
and
what
we're
playing
for
the
upcoming
Milestone.
So
first
up
we're
continuing
our
work
with
adding
support
for
Ruby
3.0.
We
have
until
I
think
believe
in
March
utility
of
life
for
Ruby
two
seven.
A
The
good
news
is
we're
about
80,
complete
now
with
the
Ruby
3
gem
audit,
which
is
a
huge
step
forward.
Huge
progress
thanks
to
everyone,
who's,
contributed
all
the
different
teams,
who've
pitched
in,
and
thank
you
for
Tim
Matthias
for
spearheading
that
effort
and
getting
everything
coordinated.
A
We're
on
track
at
this
point
I
think
to
be
able
to
switch
fully
over
V3
before
the
end
of
life.
Our
current
step
after
the
gem
audit
is
taking
action
on
fixing
up
and
cleaning
up
into
the
gyms
that
need
action
that
aren't
currently
compatible
with
Ruby
three
we're
very,
very
close
to
having
our
first
Green
Ruby
3
pipeline,
including
QA
and
and
test,
which
should
be
achieved
in
15.7.
We
also
put
together
a
pre-release
checklist
that
has
all
the
dependencies
and
things
that
need
to
get.
A
We
need
to
coordinate
in
order
to
fully
switch
over.
Some
of
those
things
are
application.
Performance
is
responsibility
and
there's
other
things
that
are
not
such
as
making
qdk
compatible
with
Ruby
3.0,
but
in
15.7
we
will
be
done
fully
done
with
Ruby
gym
a
gem
audit
effort,
and
we
also
will
have
a
green
pipeline
hopefully,
and
how
that's
working
now
is
every
two
hours
we're
running
Maine
against
Ruby
three
three.
A
So
that
way,
we're
not
consuming
too
much
resources
and
then
we'll
continue
to
run
our
normal
pipelines
on
mergers
into
Master
against
two
seven.
So
we
can
kind
of
run
both
side
by
side
as
we
transition
over
the
next
coming
months.
So
great
effort
team
excited
to
continue
to
make
progress
in
the
next
release.
B
Yeah,
the
next
major
Topic
in
the
following
Milestone
is
investigating
Puma,
long-term
memory
use
and
in
previous
Milestone
we
finally
finished
and
rolled
out
diagnostic
reports
framework
which
allows
us
to
receive
diagnostic
data
from
our
Boomer
instances
for
to
analyze
it
and
in
current
Milestone
we
will
Implement
Ruby
hip,
dump
report.
We
should
provide
us
valuable
insights
and
which
would
help
us
to
diagnose
memory,
leaks
and
high
hip
fragmentation
and
will
also
address
digital
follow-ups
related
to
this
Epic.
C
Thank
you.
So
in
157
we'll
continue
working
on
the
fine
tuning,
the
memory
killer
for
our
puma
and
psychic
processes.
We
have
implemented
a
new
memory
killer,
which
is
way
called
memory
washed
out.
So
we
hope
to
show
that
out
for
both
SAS
and
self-managed
deployments
in
the
next
Milestone,
and
maybe
in
the
next
few
months,
so
we
are
improving
the
psychic
memory
killer.
We
hope
to
also
to
replace
with
the
Watchdog
so
that
we
will
consolidate
our
other
Process
Management
tools.
C
First,
we'll
be
working
on
our
FS
memory
limit
based
monitor
that
will
be
working
together
with
the
circuit
memory
period
so
that
first
we
will
mimic
the
existing
behavior
before
we
completely
replace
it.
That's
for
the
memory
other
than
the
features
we
just
talked
about.
We
also
have
a
few
additional
issues
we
may
consider
working
on
in
15
7,
including
used
radish
ACL,
to
restrict
access
to
certain
commands
from
our
rules.
Application
we'll
also
have
some
metrics
related
issues.
C
Then
we'll
have
a
issue
that
related
to
our
psychic
load
and
load
balancing
strategy.
We
saw
some
liking
between
the
matter
and
red
cards.
There's
some
issue
that
we'll
look
into
and
address
those
issues
if
we
have
time
and
then
we'll
be
also
working
on
some
of
issues
that
related
to
our
new
GitHub
metric
exporter
by
working
on
this
issue,
we
hope
also
to
onboard
more
developers
on
this
new
project.