►
From YouTube: GitLab 14.1 Kickoff - Enablement:Memory
Description
Kickoff for the 14.1 release for the Memory team.
Planning issue: https://gitlab.com/gitlab-org/memory-team/team-tasks/-/issues/95
A
Hello
friends
of
well-performing
endpoints
and
application
performance
aficionados,
my
name
is
fabian
simmer
and
I'm
a
group
product
manager
for
the
enablement
stage.
I'm
going
to
walk
you
through
our
plans
for
the
memory
team
for
the
14.1
release,
so
the
first
minor
release
after
our
major
release
in
june
2021.
A
A
To
give
you
the
context
here,
we
run
a
postgres
postgresql
backend
for
gitlab
and
sidekick
for
job
processing,
and
so
in
order
to
to
improve
the
overall
performance
of
that
system,
we
are
focusing
on
enabling
sidekick
to
use
read-only
database
replicas
for
some
of
their
workers
to
reduce
the
load
on
the
primary
postgres
instance.
So
this
should
essentially
spread
the
load
among
different
postgres
instances
and
help
with
overall
system
performance.
So
we've
done
already
a
lot
of
work
here,
and
this
is
specifically
about
sort
of
some
follow-up
work
for
a
subset
of
these.
A
These
workers-
and
this
is
something
that
we're
going
to
going
to
do
in
in
14.1.
There
are
some
other
sidekick
workers
that
we
hope.
Other
teams
in
the
company
will
also
move
to
realize
those
performance
benefits.
So
that's
number
one.
A
The
other
thing
is
that
at
this
moment,
in
time,
gitlab
is
actually
not
using
ruby.
3
ruby
3
was
an
exciting
release
in
the
in
the
ruby
world
at
the
essentially
the
beginning
of
2021.
A
It
was
just
released
at
the
end
of
december
2020
and
you
know,
you've
maybe
seen
some
of
the
highlights
in
terms
of
performance
increases.
Obviously
this
is
a
complex
area,
so
it's
not
going
to
be.
We
upgrade
to
ruby
3
and
then
everything
will
magically
be
super
fast,
but
ruby
3
has
many
interesting
performance
improvements
and
we
hope
to
be
able
to
take
advantage
of
some
of
them,
so
we've
recently
completed
a
an
upgrade
to
rail
6.1
and
that
actually
unblocks
the
effort
of
moving
to
ruby
3..
A
As
you
can
see,
this
is
actually
a
rather
sizable
chunk
of
work,
just
because
gitlab
is
a
complex
application
and
moving
the
ruby
version
to
three
will
also
entail
updating
many
of
the
gems
and
other
parts
of
the
system
to
support
it.
So
we're
quite
excited
about
it,
because
we
do
hope
that
you
know.
Staying
close
to
the
latest
group
releases
ensures
that
you
know
we
can
benefit
from
some
of
the
new
features
and
overall
performance
improvements.
A
Lastly,
this
is
a
bit
more
theoretical,
so
essentially
we're
trying
to
move
gitlab
into
a
state
where
we
only
use
the
code
that
is
really
needed
for
all
of
the
dependencies
that
can
help
reduce
the
overall
memory
footprint
and
we've
had
a
successful
poc
by
one
of
our
team
members
and
for
us,
it's
actually
going
to
be
quite
interesting
to
think
about
what
is
needed
now
to
move
from
a
proof
of
concept
to
production
for
a
specific
component
of
of
gitlab,
and
so
this
is
something
that
we're
going
to
going
to
investigate
break
this
down
a
little
bit
further,
because
this
is
actually
going
to
be
quite
impactful
in
an
ideal
world.
A
You
know
being
able
to
only
know
what
you
need
would
reduce
the
overall
footprint
of
the
application
quite
significantly,
so
we're
very
excited
about
that
one
and
that's
it.
Thank
you
very
much
for
listening
and
I'm
looking
forward
to
14.1
take
care.