►
From YouTube: GitLab 13.10 Kickoff - Enablement:Memory
Description
Kickoff for the 13.10 release for the memory team.
Planning issue: https://gitlab.com/gitlab-org/memory-team/team-tasks/-/issues/87
A
A
So
we
have
three
main
initiatives
that
we're
going
to
follow
throughout
13.10.
The
first
one
is
we're
going
to
wrap
up
our
work
in
making
github
easier
to
run
in
a
memory
constrained
environment.
A
Some
other
configuration
changes
to
provide
a
baseline
measure
for
what
you
can
expect
of
gitlab
in
13.10,
and
finally,
we
may
be
able
to
optimize
some
ruby
settings,
some
garbage
collection
settings
for
for
italy,
so
we
can
look
into
that
as
well.
A
The
second
item-
and
this
is
a
poc,
so
proof
of
concept-
there
is
an
investigation
and
some
great
work
by
one
of
the
team
members
on
providing
a
mechanism
to
load
graphql
with
all
dependencies
only
when
needed.
So
this
is
actually
a
part
of
our
overall
push
for
splitting
the
application,
maybe
into
more
functional
parts,
so
that
we
only
load
dependencies
that
are
needed,
and
so
the
poc
here
is
also
wrapping
up
and
the
expected
outcome
for
13.10,
for
this
is
an
architectural
blueprint
for
this
type
of
compartmentalization
in
the
future.
A
Also
measuring
the
impact
of
the
proposed
changes,
and,
last
but
not
least,
one
of
our
team
members
has
recently
hatched
ruby
so
that
it
becomes
easier
to
understand
specifically
what
parts
of
the
application
use.
What
memory-
and
this
is
well
on
the
way
for
13.9,
so
we'll
start
actually
investigating
in
13.10
how
to
make
use
of
this
new
data
analyze
it
and,
ideally
start
our
effort
to
map
features
to
their
memory
reuse.
A
So
this
is
beginning
kind
of
trying
to
really
dig
into
specific
parts
of
the
application,
how
they
consume
memory,
and
this
is
it
so
for
13.10.
A
We
expect
to
wrap
up
our
effort
here,
maybe
we'll
still
fit
in
a
few
low-hanging
fruit
if
we
can
find
them,
but
also
provide
documentation
and
instructions
on
how
to
reduce
memory.
Consumption
of
gitlab
in
two
gigabytes
we're
working
on
these
larger
changes
here
it
will
take
a
while
to
realize
that
it's
the
beginning,
it's
the
proof
of
concept,
but
it
will
set
us
into
an
interesting
path
and
direction
forward
and
then
we're
trying
to
understand
the
memory
use
of
specific
features
of
the
application
other
than
that.
A
We
are
also
going
to
evaluate
a
little
bit
more
closely.
What
other
areas
are
sort
of
ripe
for
the
picking
of
the
memory
team,
where
we
can
have
the
largest
impact
going
forward
and
we'll
keep
you
posted
in
our
next
video.
Thank
you
so
much
for
listening
and
have
a
great
day.