►
From YouTube: GitLab 15.9 Kickoff - Enablement:Gitaly
Description
Planning Issue for Gitaly - https://gitlab.com/gitlab-org/gitaly-planning/release-planning/-/issues/7
A
A
My
name
is
Mark
Wood
I
am
the
product
manager
for
gidly.
As
always,
if
you
have
any
feedback,
questions
or
comments,
please
reach
out
to
me
directly
or
out
to
the
team
on
our
issues
and
our
boards
we'd
love
to
hear
from
you,
for
you
know,
additional
collaboration,
any
ideas
you
might
have
to
make
our
product
even
better,
either
note
this
month's
capacity
should
be
on
par.
There
are
no
known
events
at
present
this
month,
so
we
expect
to
see
a
normal
month
with
normal
capacity.
A
As
always,
the
direction
page
has
a
what's
next
and
why
section
that
is
updated
regularly
if
you're
interested
in
understanding
our
objectives
and
themes
as
we
move
forward,
that's
a
great
place
to
start
for
engineering
priorities.
This
month
we
are
working
very
hard
to
improve
the
repository
maintenance
strategy
for
large
repositories.
A
lot
of
our
users
are
using
large
model
repos
and,
as
a
result,
sometimes
the
maintenance
strategies.
A
Don't
work
as
well
on
those
larger
repositories,
we
have
some
very
good
opportunities
here
to
improve
performance
and
improve
repository
maintenance
and
efficiency,
so
we're
working
hard
to
implement
those.
The
first
thing
that
we're
pretty
excited
about
is
to
implement
the
multi-pack
indices
as
part
of
a
maintenance
job.
A
This
is
something
that
has
been
released
in
the
last
little
while
by
getting
and
made
even
better-
and
this
goes
back
to
the
idea
of
being
able
to
pack
not
only
the
files
for
a
single
pack
file,
but
you
can
also
multi-pack
and
repack,
and
it
creates
new
pack
objects,
they
point
to
the
newer
copies
and
it
improves
efficiency
quite
a
bit.
This
is
a
pretty
good
graphic.
There's
a
lot
more
information
out
there.
If
you're,
interested
and
I
can
go
into
more
detail
in
another
video
if
necessary.
A
The
other
thing
we're
looking
to
do
is
to
start
using
craft
packs
in
repository
maintenance.
This
is
sort
of
along
the
same
lines.
This
is
a
feature
introduced
in
get
version
2.37,
and
it
keeps
us
from
exploding
unreachable,
packed
objects
into
loose
objects.
So
now,
when
we
repack
a
repository,
we'll
be
able
to
take
all
of
those
loose
objects
and
put
them
something
called
the
cruft
pack,
this
ensures
that
we
can
download
that
craft
pack
instead
of
having
to
download
all
the
loose
objects
and
it
should
improve
efficiency.
A
We
are
also
looking
to
continue
improving
Gilly
cluster
data,
consistency
and
safety.
That's
been
an
ongoing
theme
of
ours.
In
addition,
there's
a
new
version
of
Git
Version,
2.39
and
we'd
like
to
upgrade
Italy
closer
our
giddly
as
they
comes
in
the
gitlab
package
to
this
newer
version
of
get
to
get
all
the
new
features
there
we're
also
working
very
hard
to
make
progress
on
allowing
giddly
to
push
back
on
traffic
surges.
A
This
is
something
we're
doing
to
improve
our
internal
performance
and
to
alert
those
calling
us
via
API
when
we
are
busy
and
to
better
propagate
error
messages.
So
it's
clear
when
things
don't
work
as
expected,
it
also
allows
us
to
push
back
on
traffic
surges
so
that
the
caller
can
rate
limit
calls
to
us,
thereby
ensuring
that
you
know
appropriate
performance
is
maintained
and
it's
understood
where
the
delays
are
and
how
much
you
can
push
on
a
gitly
server.
A
A
We
are
also
continuing
to
update
object,
pools
to
work
correctly
with
giddly
cluster
there's
another
issue:
we're
trying
to
tackling
this
month
along
the
same
sort
of
trend,
trying
to
do
a
little
bit
of
work
each
month
to
improve
this.
This
month,
we're
looking
to
create
or
convert,
create,
Fork
to
transparently
handle
object,
pull
creation.
A
Finally,
we
worked
very
closely
with
our
quality
counterparts
and
we
have
identified
a
handful
of
quality
issues
here
that
we
want
to
take
care
of,
so
we
are
working
through
those
as
well,
and
those
can
be
seen
in
our
bug.
Prioritization's
license
dashboard,
which
is
an
internal
dashboard,
but
you
can
also
filter
bugs
based
on
59,
and
this
allows
us
you
know
to
see
what's
going
on
within
Italy
itself,
there's
always
a
link
to
this
planning
issue
will
be
in
the
video
below
I.