►
From YouTube: Enablement Section GC Overview for 22-06-2020
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
Hi,
I'm
josh
lambert,
the
group
product
manager
for
our
enablement
section
and
I'd
like
to
give
folks
a
quick
overview
of
what
we've
been
up
to
in
this
section
in
preparation
for
our
monday
group
member
station
june
22nd.
A
A
So,
let's
jump
into
it
first
off
a
really
quick
introduction
on
who
we
are
in
case
folks
aren't
familiar.
So
the
enablement
section
is
a
bit
different
than
the
other
sections
I
feel
like
in
that
we
aren't
as
focused
on
user
facing
features.
We
do
have
global
search
as
part
of
the
section
which
is
looking
to
help
users
find
what
they
are
seeking
in
their
product
across
all
of
our
features,
but
for
the
rest
of
the
groups.
A
We're
focused
on
making
sure
that
the
operational
aspects
of
gitlab
are
fantastic
and
so
that
administrators
of
of
an
instance,
whether
you're,
a
gitlab.com
or
a
self-managed
user,
can
deploy
gitlab
easily
upgrade
it
making
sure
it
stays
up
and
running
and,
of
course,
is
performant
and
provides
users
with
a
great
user
experience,
and
so
that's
kind
of
what
the
distribution
geo
memory
database
teams
are
focused
on.
As
you
might
see
here,
we've
also
added
product
management
support
for
our
infrastructure
department.
A
This
is
a
new
change
with
the
edition
I'll
just
jump
right
over
to
it
of
andrew
thomas
with
enter
thomas.
We
have
completed
our
hiring
process
and
he
is
our
new
principal
product
manager
for
the
infrastructure.
You'll
be
providing
a
lot
of
support
to
both
the
delivery,
scalability
and
overall
com
infrastructure
teams
and
helping
to
make
sure
that
they
have
the
help
they
need
and
also
can
focus
on
some
of
the
aspects
of
gitlab.com
that
aren't
related
to
a
particular
other
section
right.
A
So
there's
a
bunch
of
features
and
those
features,
of
course
how
they
work
on
github.com
is
a
responsibility
of
those
stages,
but
there's
some
details
on
gitlab.com
that
aren't
tied
to
a
particular
feature
or
stage,
and
so
we're
looking
forward
for
andrew's
help
there
as
well.
A
A
You
can
review
the
category
maturity
there.
I
think,
on
your
own
time.
We
are
driving
forward
with
some
interesting
and
compelling
improvements
here
for
both
zest,
recovery
and
geo.
We're
aiming
to
have
all
data
types
replicated
here
in
the
next
couple
of
months
and
really
looking
forward
to
that
being
available
for
our
users.
One
exception
is
as
pages
the
current
architecture
is
quite
hard
to
replicate
with
geo
and
the
benefit
here.
A
Well,
the
other
factor
is
that
it's
possible
to
regenerate
pages
by
simply
running
rerunning
the
publishing
pipeline,
and
so
if
this
is
not
content
which
is
gone,
it
just
needs
to
be
republished,
and
so
it's
not
as
concerning
as
potentially
other
data
types
or
if
they
weren't
replicated
the
content,
simply
wouldn't
be
there
at
all.
So
again,
looking
forward
to
having
those
aspects
move
up
in
maturity
for
geo-replication
and
disaster
recovery,
the
team
has
done
a
great
job
and
we're
also
looking
to
continue
to
improve
the
cloud-native
installation
as
well.
A
All
right,
so,
next
up,
let's
talk
about
some
performance
indicators.
First,
we
have
our
metrics
review
on
thursday
at
8
am
pst,
please
join.
If
you
would
like
to
attend
we'll
go
over
these
in
more
detail
down
below.
You
can
see
that
we
have
a
periscope
topic
link
and
you
can
get
a
full
sense
of
our
metrics
there.
Please
check
them
out.
A
couple
highlights
here
to
talk
about
one
is
that
we've
recently
added
a
effectively
a
net
new
instance
chart.
A
So
rather
than
showing
you
the
total
instances
and
kind
of
inferring
the
slope.
We
now
show
you
exactly
how
many
net
new
instances
we
found
that
we're
reporting
in
uniquely
for
that
particular
week,
and
you
can
see
that
we're
tracking
about
the
same,
but
it
has
gone
up
from
about
8
000
to
around
9
000
average
installations
per
week,
and
this
is
a
12
moving
average.
So
it
is
turning
up,
which
is
great.
A
A
A
The
big
outlier
here
is
committee
edition
it's
bordering
on
almost
a
year
for
the
median
age
and
that
that's
that's
something
that
we
want
to
try
and
see
if
we
can
help
to
address.
A
These
are
users
who
aren't
seeing
any
of
the
benefits
of
the
recent
versions,
like
git
lab
right
all
that
content
month
release
posts
they
aren't
being
able
to
leverage,
and
so
we
need
to
try
and
think
about
better
ways
to
help
our
ce
users
continue
to
see
the
benefits
of
gitlab
in
our
monthly
releases.
So
that's
one
thing
you
want
to
try
and
track
and
I
think
hopefully
try
to
pull
down
in
the
future.
A
You
can
also
see
we're
continuing
to
track
other
other
aspects,
elasticsearch
with
users
being
enabled
and
geo,
we'll
cover
those
in
more
depth
later
on.
So
let's
move
on
engineering
metrics.
You
know
we're
a
little
bit
under
on
the
time
to
merge
and
mrs
per
engineer
I'll.
Let
china
comment
on
this
in
more
detail
later
on
monday,
but
we're
definitely
tracking
these
and
keeping
an
eye
on
them
as
well.
A
We
haven't
had
significant
changes
to
our
priorities,
so
definitely
check
out
our
enablement
section
for
a
more
complete
list
of
what
we're
focused
on
and
why.
But
these
are
essentially
largely
continuing
to
make
progress
in
these
larger
themes.
A
We
are
continuing
to
focus
on
dog
fooding,
we'll
talk
more
about
patrony
in
a
little
bit
in
more
detail.
We
are
continuing
to
work
on
that
to
essentially
provide
to
our
customers
the
same
tool.
Tool.Com
is
using
for
database
replica
database
load,
balancing
and
failover,
and
so
that's
underway
now-
and
you
can
see
some
other
updates
here
on
the
releases
feature
and
some
other
influences
cng.
A
A
Here
it
does
contain
some
more
detailed
business
information,
and
so
that's
why
it
is
not
being
shared
publicly
but
in
general,
fabulous
a
great
job
in
identifying
users
using
things
like
zendesk,
above
and
beyond
what
is
available
in
the
usage
ping
and
has
used
that
to
help
generate
a
target
profile
for
a
customer
where
geo
can
really
help
them,
and
so
you
can
see
in
this
case
what
that
looks
like
generally
500
to
1000
seats
or
above
large
enterprise
right
compliance
requirements.
A
Also
is
a
key
driver
for
geo
right
if
they
have
to
manage
business
continuity
or
just
recovery,
or
they
have
more
than
one
location.
Those
can
be
areas
where
geo
can
really
really
help.
A
So,
given
that
customer
profile
that
we
have
papian
took
the
next
step
and
identified
accounts
that
are
on
starter,
that
meet
that
target
profile
and
may
benefit
from
geo
and
similarly,
customers
who
already
have
access
to
geo
and
premium,
but
are
not
currently
using
it
and
so
we'll
be
going
through
and
actioning
those
lists
and
working
to
hopefully
make
sure
that
these
customers
are
aware
of
geo
and
its
benefits.
A
Other
key
facts
here
about
geo.
Interestingly,
we
have
around
85
accounts
that
use
geo
currently,
but
those
85
accounts
represent
25
of
the
premium
seats
and
of
those
those
represent
13
of
our
total
ar
for
gitlab
is
customers
who
utilize
geo,
so
some
great
numbers
there
and
again.
If
you
have
questions,
please
phrase
them
on
monday
and
we'll
be
happy
to
answer
them.
A
As
I'm
not
going
to
focus
on
the,
in
particular
the
the
plans
for
distribution
and
the
other
groups
because
number
one,
if
you
want
to
take
a
look
at
the
what
we
plan
for
13.2,
please
do
look
at
the
kickoff
videos.
Those
do
a
great
jobs
on
our
direction.
Change
of
explaining
what
we're
focusing
on
and
why
and,
of
course,
also
the
release
post,
which
is
now
available.
A
One
area
do
you
want
to
focus
on
here
is
petroni.
I
mentioned
a
bit
earlier,
and
this
is
a
key
change
for
our
customers.
They
will
be
migrating
away
from
rep
manager,
which
has
been
our
previous
solution
for
postgres
or
multi-node.
Postgres,
failovers
and
petroni
is
what
using
github.com
isn't
working
very
well
for
us
and
so
we're
looking
forward
to
bringing
those
benefits
to
our
customers
number
one.
We
have
seen
a
few
situations
where
rent
manager
had
some
problems.
A
We
don't
think
petroni
has
those
and
so
we're
looking
to
resolve
those
with
the
with
this
new
solution,
but
it
also
enables
us
to
have
two
key
improvements
or
three
three
key
improvements.
A
Previously,
we
only
supported
signal
node
secondaries
with
rep
manager.
Finally,
we've
also
further
automated
the
process
where,
if
you
do
have
a
situation
where
a
node
of
postgres
goes
down,
bringing
a
failed
map
after
failed
back
into
the
cluster
is
now
automated.
Previously,
with
threat
manager.
You
had
to
take
some
manual
action
so
looking
forward
to
bringing
that
to
our
customers
and
we're
focusing
on
announcing
it
here
in
13.2,
really
quick
on
the
postgres
roadmap
I'm
going
to
highlight.
A
A
This
is
one
of
those
changes
where
it's
very
complicated
and
there's
a
the
potential
for
sort
of
fireworks
is
high,
and
we
have
seen
very
very
few
and
no
major
issues,
and
so
I
really
want
to
give
a
thanks
to
the
team.
Who've
worked
on
this
and
also
puma
as
well.
Bringing
those
benefits
again
without
significant
disruption
to
our
users
is
great
to
see
again.
A
These
are
one
of
those
things
that,
if
you
do,
if
you
do,
if
you
do
it
correctly,
you
know
the
best
case
scenario
is
essentially
no
news
is
good
news,
and
so
I
wanted
to
highlight
that,
because
that
is
the
case
so
far
with
these
so
really
great
job.
A
As
far
as
postgres
12
goes
again,
we're
working
on
petronium
to
enable
support
for
it,
but
also
just
the
fact
that
we
have
support
for
this
allows
us
to
take
advantage
of
the
new
engine
features
and
so
overall
by
simply
upgrading
the
pg-12
will
have
a
faster
performance
of
get
lab
and,
in
particular,
we've
been
working
on
partitioning
for
the
database
side
and
in
pg
11.
A
We
think
this
would
be
a
a
really
huge
benefit
to
our
users
to
accelerate
their
time
to
value,
to
reduce
the
investment
they
have
to
make
it
up
front,
to
start
to
see
some
great
returns
and
will
also
help
us
make
sure
that
users
are
deploying
reference
architectures,
as
we
have
seen
great
results
in
and
you
just
using
those
as
opposed
to
some
of
the
other
kind
of
customized
architectures,
where
there
have
been
performance
problems.
So
again,
this
is
a
really
key
feature
for
us.
A
Again,
please
pay
attention
to
our
kickoff
videos
if
you
have
a
chance
and
or
watch
the
overall
one,
some
great
content
there
for
geo
and
we
are
focused
on
a
number
of
areas
I'll
skip
over
this
and
please
read
through
where
we're
going
in
the
category
directions
and
bring
your
questions
on
monday.
So
we
can
answer
them
in
the
event
that
you
do
have
any
of
them.
A
I
do
want
to
pause
here,
really
quick
and
highlight
one
aspect
of
global
search
which
has
been
great
to
see,
and
that
is
that
we
have
accelerated
the
deployment
of
advanced
global
search
which
allows
for
code
search
for
paid
groups
on
gitlab.com,
and
we
expect
to
be
complete
on
july
15th.
It's
a
great
improvement
for
we're
looking
at
before,
and
we
already
have
100
of
all
bronze
users
already
indexed
today
on
gitlab.com,
and
you
can
see
some
of
those
metrics
here.
A
As
far
as
what
that
looks
like
so
number
one
you
can
see
that
we
started
off
pretty
slowly.
We
had
a
number
of
things
to
fix,
as
we
tried
to
make
sure
that
advanced
global
search
can
scale
to
the
size
of
gitlab.com
and,
as
we
made
some
changes,
further
improvements,
we've
been
able
to
really
ramp.
This
up,
which
is
which
is
really
great,
to
see
so
again
expect
this
to
be
complete
in
july
15th,
and
you
can
see
a
resulting
increase
in
the
number
of
search
volume
using
advanced
global
search
on
gitlab
as
well.
A
One
quick
note
is
that
we've
also
been
able
to
decrease
the
size
of
the
index.
We've
decreased
it
last
release
by
about
75
percent,
for
a
total
decrease
in
elastic
search
cost,
which
is
what
powers
advancement
will
search
by
about
80,
so
good
cost
savings
there
for
gitlab.com,
but
also
for
all
of
our
customers.
A
So
with
that,
I
think
we
have
reached
the
end
of
what
I
wanted
to
highlight
for
our
our
video.
Here
again,
please
do
look
through
the
slides
and
bring
your
questions
and
also,
of
course,
our
category
strategies,
our
videos
and
the
overall
release
post
worth
in
that
one
great
content,
and
there
are
super
amazing
release
by
the
entire
team
and
again
looking
forward
to
talking
with
you
on
monday.