►
From YouTube: GitLab 13.0 Kickoff - Enablement:Memory
Description
13.0 Kickoff for the Enablement:Memory group
A
Hi
I'm
Joshua
Lambert,
a
product
manager
here
at
Gilliland
and
I'd,
like
about
what
the
memory
team
is
working
on
for
our
13
double
release.
The
first
thing
we're
working
on
is
finishing
up
a
few
projects
that
we've
had
in
flight
from
our
previous
release.
Last
release
called
at
10:00
we're
working
on
deploying
some
additional
flexibility
in
how
we
price
our
shared
runners
on
github.com.
This
will
allow
us
to
offer
additional
runner
types
like
mac
and
Windows
runners.
A
We're
also
working
on
finishing
out
a
couple
other
items
that
are
just
really
close
to
being
done
here.
This
is
an
improvement
to
the
import
workflow,
which
we
are
wrapping
up.
It
is
interview
and
from
there
we
are
now
working
more
or
to
focus
a
little
bit
more
towards
the
overall
performance
of
gallop
calm.
The
first
thing
we
like
to
do
here
is
to
work
on
getting
some
performance
metrics
on
common
user
journeys
in
Gale
app,
and
this
is
real
world
real
browser
performance,
metrics
right.
A
If
we
able
to
get
some
timings
on
those
that
have
common
jus
journeys,
I
think
it
can
help
to
illustrate
some
of
the
performance
areas
we
have
that
we
can
improve
as
well
also
paint
a
more
consumable
and
digestible
picture
of
the
impact
of
some
of
these
performance
opportunities.
We
have
so
the
product
managers
and
the
other
product
groups
we
had
can
help
to
prioritize
them.
A
It's
just
a
bit
more
tangible
when
you
say
that
it
takes
perhaps
four
seconds
to
go
to
the
to
do
is
to
go
to
the
issues,
leave
a
comment
for
each
one.
You
do
then
to
say,
for
example,
that
a
rails
controller
is
out
of
bounds
by
X
percent,
so
hopefully
this
can
also
help
to
solve
some
of
the
prioritization
challenges
that
pipe
address
that's
a
day
and
trying
to
really
understand
the
impact
of
sales
performance
issues.
A
It's
the
good
thing
here
is:
we
can
track
these
earnings.
We
already
have
a
number
of
them
as
a
Christian
know
that
down
below
in
this
issue,
around
kind
of
are
you
a
space
line
scores,
and
so
we
can't
you
get
a
performance
benchmark
attached
to
these
new
x-gen
ease
and
then
monitor
bleeds
over
time.
Of
course,
within
the
day,
understand
how
they
changed,
also
from
release
to
release,
to
release,
to
make
sure
we're
actually
improving
the
performance
of
these
workflows
over
the
next
couple
of
releases.
A
So
I'm
particularly
excited
about
this
and
I.
Think
it's
a
great
way
for
us
to
help
to
provide
some
broader
hi.
A
little
context
on
the
performance.get
lab
from
here.
We're
also
working
as
part
of
the
real
time
working
group
and
so
Matthias
is
working
on,
introducing
some
actions
table
still
and
support
and
to
our
gck,
and
so
that
we
can
do
some
further
development
work
and
the
container
kit
forget
labs
and
help
to
work
into
that
work
forward.
A
And
finally,
we
also
would
like
to
work
in
partnership
with
the
infrastructure
team
to
enable
the
shrewdest
tracy
and
get
lab
calm.
We've
had
some
inspiration
available
in
an
experimental
form
was
available
in
the
GDK
already
for
Yeager,
but
we
have
it
enable
it
on
comm
as
of
yet-
and
this
would
be
beneficial
because
it
can
provide
some
really
rich
insights
into
the
application
performance
and
a
multiple
service
distributed
way
and
should
hopefully
help
us
to
accelerate
some
troubleshooting
and
understanding
of
where
some
of
the
performance
challenges
are
in
real
time
and
it's
happening.
A
I'm
get
left
calm
as
opposed
to
having
to
go
through
and
try
to
do
some
analysis
after
the
fact
that
you
know
the
problem
is
corrected
itself,
so
I'm
a
priest
about
this
and
with
the
cash
you
get
this
other
comm,
we
have
to
do
it
in
a
tool
selection.
Here
we
do
kind
of
pick
from
jäger,
which
is
partial.
Today
our
option
is
elastic
APM
and
some
kind
of
need
to
do
some
analysis
here
and
then
go
ahead
and
work
to
get
this
instrumented,
but
about
work
actually,
probably
isn't
that
much
I.
A
Have
you
lift?
That's
the
memory
team
I
was
more
than
happy
to
help.
Do
whatever
takes
the
engineering
side,
but
likely
the,
and
it
depends
on
what
good
solution
to
go
with
with
a
Jaeger
or
elastic
more,
the
work
will
likely
land
on
the
infant.
Did
the
infant
team
actually
depending
on
I,
didn't
worry
solutions.
Takers
like
be
a
little
heavier
on
the
in
facade,
whereas
elastic
likely
could
be
quite
minimal
outside
of
the
engineering
work.
Mainly
because
doesn't
you
know
we
don't
have
to
run
our
own
service?
A
So
that's
our
exciting
I've
been
here
for
our
memory
team,
really
looking
forward
to
help
to
capture
some
better
metrics
in
the
overall
performance
of
gitlab
and
hopefully
set
some
good
foundational
services
and
data
really.
So
we
can
improve
the
prone
to
get
live.com
here
in
the
next
couple
releases
building.
On
top
of
this
work
here
in
30
note,
oh
thank
you
and
look
forward
to
delivering
this
to
you
on
this
release.