►
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
Hello,
everybody,
my
name
is
Roger
and
I
am
the
senior
product
manager
supporting
the
application,
Performance
Group,
and
today
this
is
our
15.10
planning
video
in
1510.
The
application
team
will
be
operating
at
approximately
70
capacity.
In
particular,
Nikola
will
be
away
for
two
months
on
paternity
leave.
We
expect
to
return
at
the
end
of
1511
on
April
15th.
A
Our
top
priority
is
for
1510
continues
to
be
Ruby
3.0.
Our
general
focus
as
a
team
is
Shifting
away
from
memory
optimizations
to
exploring
other
areas
of
perceived
performance,
we're
curious
to
see
the
results
of
some
application
profiling
and
to
investigate
real-time
capabilities
for
gitlab.
First
up
Ruby
version
3.0.
We
are
currently
on
track
for
Ruby
3
production
rollout
in
15.10.
We
have
scheduled
a
hard
production
change
lock
on
March
7
2023
for
the
SAS
cut
over.
A
We
are
also
time
boxing
and
exploration
to
identify
cross-cutting
opportunities
to
improve
gitlab's
application
speed.
We
are
assessing
Google
Cloud
profiling
for
Ruby
and
we're
curious
to
see
if
there's
any
low
hanging
fruit
for
optimization
and
improvements
that
we
can
identify.
We
will
deploy
this
in
1510
and,
if
there's
anything
we
can
identify
as
an
improvement,
we
will
Target
those
efforts
in
1511
onwards.
A
A
The
team
doesn't
have
much
familiarity
with
this
domain
and
will
need
some
time
to
ramp
up
there's
two
different
types
of
real-time
Solutions
at
gitlab
today
for
incremental
real-time
features
and
collaborative
text
edit,
we
are
prioritizing
a
context
transfer
from
the
real-time
Tech
status
sitting
group
due
to
a
team
member
departure
on
March
16th.
This
means
that
other
real-time
related
research
will
likely
be
pushed
to
15.11.
A
There
are
a
few
items
that
the
team
is
closing
at
three.
In
particular,
we
wanted
to
draw
attention
to
First
is
gitlab's
metrics
exporter,
so
we're
going
to
pause
the
rollout
of
this
effort,
because
currently
we
decided
that
there's
not
a
lot
of
root
cause
for
memory,
spikes
that
we're
able
to
identify
so
we're
going
to
switch
our
Focus
to
higher
priority
items.
A
A
We
recognize
that
scychic
is
a
very
big
topic
and
there
will
likely
be
Memory
saturation
issues
crop
me
up
again
in
the
future.
However,
we
believe
our
investments
to
date
have
put
gitlab
in
a
stable
position
and
so
we're
going
to
pause
this
work
stream
at
this
time.
Lastly,
is
the
Puma
long-term
memory
use
investigation.
We've
spent
a
few
Milestones
exploring
this
space
and
we
still
do
not
have
a
strong
hypothesis
on
what
might
be
the
underlying
cause.