►
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
Hello,
everybody,
my
name
is
Roger
and
welcome
to
the
application
performance
groups.
15.9
planning.
Today,
we've
got
a
bit
of
a
bigger
group
than
usual,
so
I
am
the
senior
product
manager
working
with
the
application.
Performance
Group
and
we've
got
three
other
people,
so
I'll
just
pass
around
for
everybody
to
introduce
themselves
so
I'll
hand
it
over
to
Alexi
to
start.
B
C
A
Cool
so
yeah
welcome
Paul
and
thank
you
CZ
for
all
your
support
over
the
past
many
many
milestones
and
we're
excited
to
see
where
this
goes
for
this
Milestone
there's
no
particular
capacity
items
to
call
out
and
in
terms
of
planning
our
top
priority
as
a
team
continues
to
be
supporting
the
Ruby
3
upgrade.
B
Yeah
so
currently
we
have
gitlab
Network
exporter
enabled
on
staging,
but
to
enable
it
production
white.
We
need
to
investigate
spikes
in
memory
usage.
That's
our
goal
for
the
next
Milestone
and
we
hope
to
resolve
it
and
make
it
production
ready
to
ECG.
D
The
next
feature
I'm
going
to
talk
about
is
the
memory
killer,
psychic
memory
killer,
so
in
159
we
will
complete
the
work
of
drawing
out
a
unified
memory
killer
for
both
Puma
and
psychic.
After
we
verified
our
member
killer,
performs,
as
expected,
will
deploy
it
across
a
GitHub
SAS
platform
and
also
will
release
it
to
self-managed
customers
and
I
will
over
to
you
Alexi
for
the
next
feature.
D
B
In
previous
milestones,
we
worked
hard
to
create
a
mechanism
to
obtain
diagnostic
reports
from
production
notes
to
investigate
memory
and
performance
issues.
Last
milestones,
we
finished
Ruby
hip
dance
report
and
as
a
strategy
goal
in
this
Milestone.
If
you
will
have
time
from
Ruby
3,
we
plan
to
investigate
the
report's
data
and
try
to
find
some
valuable
insights
regarding
how
our
system
operates.