►
From YouTube: GitLab Kick Off 12.10 - Enablement:Database
Description
Enablement:Database kickoff video for 12.10
A
Hi
I'm
Josh
Lambert,
a
group
product
manager
here
at
get
lab,
and
today
I'd
like
to
talk
about
our
guinea
based
groups,
plans
for
the
12.10
release,
which
will
be
shipping
in
April
22nd.
We
have
a
few
key
items.
We're
working
on
here,
and
one
thing
to
keep
in
mind
with
this
group
is
that
it's
a
relatively
small
group.
Currently
we
are
hiring,
and
so
please
do
check
out
our
jobs
page
and
join
the
team.
A
We're
doing
some
really
exciting
great
database
work,
especially
if
you
are
interested
in
helping
to
define
how
databases
can
continue
to
scale
with
some
really
aggressive
growth
patterns.
So
if
that
excites,
you
definitely
apply
the
team.
However,
currently
with
our
current
team
sizes,
we
do
still
have
some
really
interesting.
Projects
were
working
on
here,
so
this
is
for
the
12
10
release.
The
first
one
is
that
we
want
to
make
sure
we
communicate
our
switch
over
from
schema
that
are
B
over
to
structured
sequel.
A
The
next
item
we're
working
on
is
to
continue
to
investigate
partitioning,
so
we
did
some
investigation
in
12.9,
as
you
can
see
here
when
what
kind
of
impact
partitioning
has
on
certain
query
performance.
What
we
found
is
that
in
some
cases
it
can
have
a
significantly
negative
impact,
and
so
we're
going
to
go
ahead
and
take
a
further
look
at
this
in
this
release.
To
make
sure
the
good
understanding
of
this
and
then
figure
out
how
we
can
try
to
work
around.
A
So
that's
going
on
here
so
again
make
sure
we
have
a
solid
plan
forward
to
take
advantage
of
partitioning
to
give
us
that
additional
Headroom
and
performance
as
quickly
as
possible
once
30
nano
hits,
which
is
when
PG
11
will
become
required
and
can
take
advantage
of
these
features
like
partitioning
so
moving
on
from
there.
We
are
also
continuing
to
explore
some
other
potential
solutions.
Looking
with
a
little
bit
longer
of
a
time
horizon
around,
you
know
where
the
growth
of
gitlab
in
particular,
get
lab.
A
Comm
is
going,
and
how
do
we
prepare
for
that
growth
and
do
we
need
to
do
anything
differently
than
what
we're
doing
today?
So
one
of
those
technologies
that
were
looking
at
is
situs
T
V
as
a
potential
option
for
sharding,
and
so
you
can
see
we're
looking
at
two
simple
size
to
be
cluster
and
then
exploring
how
sharding
works
inside
this.
To
be
that's
an
interesting
benefits
like,
for
example,
allowing
you
to
shift
some
of
these
partitions
over
from
one
node
to
another,
to
kind
of
load.
A
Balance
them
as
if
initially
get
hot
other
inputs
are
also
making
here,
is
that
we
are
working
to
support
limits
for
offset
pagination
and
funding
the
default.
So
we
had
some
great
changes
that
we
made
to
build
in
a
key
based
pagination,
as
opposed
to
offset
based
pagination,
and
that
happened
a
couple
release
ago
with
some.
A
Some
really
strong
impact
on
performance
and
really
could
give
our
API
customer
is
a
significant,
improve
performance
improvement
as
they
go
deeper
into
some
of
these
pages,
and
we
Telegraph
that
we
wanted
to
correspondingly
limit
the
ability
to
go
deep
with
offset
based
pagination,
which
has
an
increasingly
higher
impact
on
performance
as
you
go
deeper
and
deeper
and
deeper
into
the
list
of
items.
And
so
we
want
to
go
ahead
and
add
a
limit
to
prevent
how
deep
you
can
go
effectively
saying
you
know
what
offset
has
some
benefits
around
things
like
filtering
and
ordering.
A
Why
density
matters
from
scheduling
jobs
and
back
of
migrations
and
some
other
improvements
here
as
well,
as
was
also
making
sure
we
have
some
good
idea
of
what
the
global
cache
hit
right
is
under
comm
service.
So
again,
some
really
exciting
changes
here
for
get
calm
and
really
forget
lab
from
the
database
team
here
in
12.10.
So
thanks,
everyone.