►
From YouTube: GitLab 13.4 4 Kickoff - Memory
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
A
Next
up,
we
want
to
continue
to
work
on
reducing
the
number
of
sql
cache
calls
that
we
make,
because
this
results
in
effectively
slower
performance
on
the
gitlab
server
side,
so
users
will
see
slower
pages
and
also
they'll,
see
admins
will
see
higher
consumption
of
compute
on
the
gitlab
server
side.
So
it's
a
win-win
for
everyone
involved.
Here
we
had
a
great
impact
here
with
the
notes
controller,
and
these
are
the
other
controllers
that
we
see
that
have
high
counts
of
cache
queries
and
so
we'll
be
targeting
these
next
here
so
effectively.
A
A
Next
up,
we
also
want
to
support
an
okr.
We
have
for
this
quarter
thursday
night
4
is
the
first
release
in
the
quarter
and
we're
targeting
improvements
to
five
of
the
most
commonly
visited
pages
on
gitlab.com
and
likely
other
github
instances
as
well,
which
is
the
project
homepage
issue
list
issue,
detail
mr
list
and
then
mr
detail
pages,
and
you
can
see
those
here.
We
want
to
improve
the
largest
contentful
paint
time,
which
is
a
metric
which
identifies
effectively
the
time
it
takes
to
deliver
most
of
the
page
to
the
end
user.
A
A
We
have
a
few
other
items
here
that
are
also
important
that
we're
working
on.
We
want
to
help
collect
the
telemetry
on
the
actual
user
experience
that
is
perceived
by
users,
and
so
we
can
currently
today
collect
the
performance
of
the
server,
but
we
don't
really
get
much
telemetry
back
on
the
performance
of
our
overall
user
base
and
we
want
to
try
and
collect
this
via
snowplow.
A
So
we
have
the
understanding
of
what
our
users
are
experiencing,
and
so
we
can
know
from
proving
things
or
not
for
our
overall
user
base
and
then
we're
also
working
on
a
few
other
things
that
will
improve
performance.
Potentially,
if
we
have
time
but
up
here
is
the
top
three
largely
aligned
around
working
to
improve
the
overall
performance
of
git
lab
that
our
users
perceive,
and
that's
a
llamas
like
opr
right
here.