►
From YouTube: 2020 10 05 Memory Team Meeting
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
All
right
welcome
to
this
version
of
the
memory
team
meeting
and
we'll
jump
right
into
it
so
top
of
the
list.
There
is
the
image
resizing
and
josh,
and
I
were
talking
about
this
earlier
this
week
he
asked
what
we
were
measuring
while
we
were
doing
the
image
resizing-
and
I
couldn't
answer
I
didn't
know
so
we
kind
of
talked
through
some
things.
He
said
you
know.
B
Is
our
priority?
I
couldn't
save
it
too
much
more.
I
was
mostly
keeping
an
eye
on,
like
general
health,
also,
of
course,
and
directly,
but
one
of
my
primary
criteria
I
was
looking
at
was
like
the
duration,
the
99
percentile
of
the
request
time
and
currently
it
sits
below
200
milliseconds,
which,
for
one
million
more
precise
images
we
serve
today
after
we
enable
fishbox
to
everyone.
B
So,
even
though
we
have
some
weird
spikes
on
maximum
duration,
they're,
not
even
a
99
personnel,
so
my
I
will
probably
look
into
these
requests
because
we
have
a
couple
of
requests
which
took
like
15
seconds,
but
maybe
it's
not
related
to
our
record
at
all.
Maybe
it's
related
to
the
whole.
You
know
this
workhorse
rails
cycle
and
there
was
a
deployment,
so
I
don't
know
yet
what
was
the
reason?
But
99
personnel
sits
like
30
below
200
milliseconds,
so
yeah,
I
don't
know
what
else
we
could.
C
B
This
side
speed,
but
I
don't
actually
know
I
didn't
okay,
so
yeah.
B
C
For
some
pages
that
will
likely
show
improvements,
like
you
know,
like
a
merge,
request,
detail
or
a
merge
request
list
page.
So
we
have
some
of
those,
so
that'll
be
helpful.
Probably
where
are
we
at
as
far
as
deployment
goes
like?
Is
it
fully
enabled
for
everything
or.
C
B
C
B
B
B
B
I
I'm
still
I'm
still
like
a
bit
monitoring
the
process
and
I
will
post
if
I
don't
need
to
roll
back,
but
I
hope
I
won't
so
now.
It's.
B
A
C
Yeah
for
now,
right
now
I'll
just
share
the
link
in
the
stock
and
or
I'll
put
them
in
the
pipe.
But
if
I
just
put
them
in
the
epic
and
then
you
know,
and
then
we
can
all
keep
an
eye
on
it
today,
like
the
test
runs
every
like
12
hours
or
so
so
it
might
take
a
little
bit
having
our
baseline
test
but
cool.
A
A
Anybody
can
contribute
to
this
blueprint.
Really
I
just
took
the
epic
and
reworded
it
to
fit
the
the
blueprint
format
and
the
reason
this
was
created
is
because
there
is
going
to
be
a
handoff
piece
right,
we're
going
to
stop
our
work,
essentially
with
the
avatar
portion
of
it,
but
there's
a
lot
more
follow-up
work
that
some
team
will
pick
up
so
by
creating
the
blueprint
that
kind
of
wraps
everything
up
and
puts
it
in
place.
A
We
can
hand
it
off
so
that
folks
know
what's
up
next,
but
I
would
say
if
you
have
any
questions
on
the
architectural
blueprint
itself
or
the
workflow
just
ask
on
the
merge
request
and,
like
I
said
anybody
can
contribute
to
the
merge
request.
I
started
the
draft,
but
it
is
not
complete.
Grigor's
asked
a
bunch
of
questions
on
there
that
I
still
need
to
get
back
to
all
right
rum
on
git
lab.
A
Lessons
learned
we've
talked
about
this
for
a
while.
I
created
that
epic
on
the
under
memory
team
tasks
and
seems
like
as
we're
ramping
down
on
image,
resizing
and
cached
queries
that
we
can
take
a
chance
to
actually
do
the
lessons
learned
write
up
some
of
the
lessons
we
learned
from
each
and
see
if
we
can
share
any
good
findings
with
the
rest
of
the
team,
both
internally
and
externally.
So
I've
added
the
issues
at
13.6.
A
Take
a
look.
I
know
that
we
have
the
the
blog
post
already
out
there
for
or
at
least
a
draft
of
the
blog
post
for
image
resizing.
So
it
would
be
good
to
get
that
out
there
and
how
we
measured
how
we
implemented
and
measured
the
cash
queries
they're
all
really
good
stories
for
lessons
so
we'll
get
those
scheduled
for
the
next
milestone.
A
Someone
added
it's
probably
nicola
added.
The
n
plus
one
cache
queries,
work.
D
D
Reordered
like
the
epic
that
now
contains
the
documentation
issues
and
I
created
a
sub
epic
that
contains
like
the
improvements
work
where
we
like
we're,
fixing
something,
and
I
think
that
currently
we
have
three
issues
that
are
almost
done
and
I
will
maybe
add
one
more,
and
I
think
that
will
be
enough
for
like
examples
and
like
we
fixed
three
or
four
and
maybe
even
five
end
points
and
then
I
will
focus
more
on
documenting
the
process
and
everything
else.
D
E
Yes,
so
I
actually
added
these
three
items,
I
I
was
like
pretty
involved
recently
with
the
zip
architecture
of
the
guitar
pages,
and
it's
actually
like
so
far
like
going
super
well,
like
you
were
running
keyclaw.com
for
the
last
week,
like
initially
for
few
hours
and
for
24
hours
until
we
decided
that
we
just
gonna
run
it
continuously,
and
I
am
planning
like
with
the
pages
team
to
start
doing
percentage
rollout.
E
E
I
actually
also
got
involved
later,
like
with
their
honor
changes.
I
just
continue
working
on
that
and
the
feature
flux.
It
seems
that
right
now
for
agenda
to
me
and
the
feature
flux
is
like
there
is
seems
to
be
agreement
to
remove
the
licensed
future
flux.
Implicit
license,
feature
flux
to
actually
kind
of
remove
around.
E
I
mean
over
100
feature
flights
that
are
in
pc
today,
so
this
is
basically
like
what
I'm
aiming
to
finish.
This
week's
for
the
future
flux
and
the
next
for
me,
gonna,
be
preparing
doc's
page
for
the
future
flux
with
the
information
of
this
is
what
I'm
being
co-copied
with.
A
A
Nope
all
right
spend
some
time
this
week
with
josh
and
probably
other
people
on
the
team
to
figure
out
the
work
that
we
need
to
do
coming
up
for
ruby
two
seven
and
we
already
have
some
issues
out
there
for
reducing
the
memory
footprint
of
get
lab
so
and
that's
all
coming
up
for
13.6.
Once
we
wrap
up
the
current
efforts
so.