►
From YouTube: GitLab 15.4 Kickoff - Enablement:Application Performance
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
Today,
I'm
going
to
go
over
our
154
planning,
we
have
a
quest,
packed
plan
for
the
coming
mouse,
so
first
we'll
continue
our
investigation
for
the
puma
long-term
memory
use
in
previous
releases.
We
have
added
abilities
to
collect
more
metrics
and
reports
to
help
us
troubleshoot
give
up
instance.
Memory
issues
in
154
will
continue
this
effort
and
plan
to
work
on
the
following
issues:
first,
we'll
add
more
ability
to
collecting
jubilee
hypnos
and
the
other
one
will
be
working
on
uploading
diagnostic
reports
to
gcs.
A
A
A
The
next
topic
is
about
investigating
and
fixing
issues
when
using
database
load,
balancing
on
psychic
workers
when
using
the
delay
strategy
for
psychic
workers
with
database
load
balancing
feature
we
found.
There
were
issues
when
replica
database
servers
fell
behind,
will
address
this
issue
and
make
sure
the
operation
will
fall
back
using
primary
database
rather
than
running
to
failures.
When
replica
dedicates
its
lagging
behind
or
become
unavailable.
A
A
A
A
A
A
will
be
more
in
a
role
of
unblocking
other
groups
and
developers
to
finish
their
work.
You
can
imagine
this
work
touches
many
parts
of
the
github
feature,
and
instance
with
that
being
said,
we
expect
to
work
on
from
the
following
aspects:
first,
we'll
collaborate
and
support
engineering
productivity
team
to
test
the
main
github
branch
against
ruby3.
A
A
We'll
also
make
sure
to
add
the
ruby.
3
builds
for
all
gitlab
libraries
and
the
next
one
is
collaborate
with
other
engineering
groups
to
refine
their
job
other
than
all
the
plan
features
and
the
maintenance
work
will
also
continue
to
monitor
the
high
severity
and
priority
issues
and
addresses
in
time.