►
From YouTube: 2022-04-04 Database Scalability WG Weekly
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
Okay,
so
I'm
going
to
start
this
is
today
is
a
pro
force.
This
is
a
database
scalability
working
group
weekly
sync
up
meeting
okay.
So
let's
get
started
from
updates
from
the
the
sharding
group,
so
phase
four
staging
road
was
completed
last
week
and
we
are
running
that
in
staging
right
now,
and
things
went
well
so
far.
So
now
the
team
is
preparing
for
the
production
rollout.
Hopefully
we
will
roll
out
this
week
and
a
second
bullet
camille
and
the
furkan.
A
They
actually
implemented
magic
to
unblock
physics,
amazing.
So
the
result,
the
testing
result.
Of
course,
some
podcasts
shows
that
the
47
times
performance
improvement
against
the
non-decomposed
version
of
the
query.
So
that's
very
impressive.
However,
this
is
still
a
temporary
workaround.
We
still
need
that
feature
to
be
re-architected.
A
To
fully
address
the
problem,
so
that
will
be.
I
think
that
work
is
going
to
happen
between
ops
and
and
starting
group,
probably,
but
mostly
as
opposed
to
feature
so
we'll
see.
A
There
is
a
timeline
we
we
want
this
to
do,
but
not
as
urgent
as
now,
because
we
are
unblocked
from
the
physics
any
questions.
B
C
B
Yeah,
I
I
I
think
we
have
to
wait
and
see
if
the
tests
finish
faster
or
not,
but
it
looks
very
promising
congrats
to
the
team,
yeah.
A
Cool
or
to
my
last
bullet
for
from
charlie,
actually
a
lot
of
great
discussions
around
the
dr
test
cases.
I
just
don't
wonder
if
you
would
be
able
to
capture
the
details
and
factor
those
into
the
one
of
the
six
scenarios
so
under
that
epic,
there
are
six
test
scenarios
a
lot
of
our
discussions,
so
whether
you
know
just
capture
the
detail
through
the
scenarios.
D
Yeah,
I
just
had
a
question
there
about
whether
we
have
a
due
date
for
that.
Yet
it
currently
says
april
8th
and
I
think,
we're
getting
to
the
place
where
we'll
need
to
be
more
crisp
about
the
the
timeline
and
everything
that
needs
to
be
done
here
so
yeah.
If
anyone
knows
it
feel
free
to
add
it.
Otherwise,
I
can
also
take
an
action
item
to
try
to
clarify
it.
A
Yeah
serbia,
in
the
community,
you
can
correct
me,
but
this
test
will
be
carried
out
in
phase
five
and
six.
We
know
those
two
phases
are
aligned
together
in
the
same
time
frame,
so
we
will
be
executing
these
test
cases
in
phase
five
and
six.
That's
upcoming.
I
think
timeline
wise
that
is
yeah.
A
pro
8
is
looks
right.
B
Yeah,
but
from
from
my
perspective,
the
due
date
will
be
a
little
bit
further
in
the
future
and
the
line
with
those
spaces.
We
can
probably
update
that,
and
it's
great
to
see
nick
westbury
also
work
on
it
actively.
I've
read
some
of
his
comments,
so
thank
you
for
it
for
that.
I
personally
think
that,
for
me,
this
would
be
important
to
have
sort
of
a
risk
understanding
of
these
scenarios
as
well
like
how
likely
are
they?
B
How
bad
are
they
so
that
we
can
make
sure
we
test
the
most
risky
things
with
with
priority
yeah.
E
Nick
has
been
reviewing
those
scenarios
and
I
will-
and
I
think
he
has
been
leaving
comments
in
there.
I
will
ask
him
to
provide
a
final
conclusions
to
it.
They
have
with
respect
to
risk
analysis
that
will
take
a
little
bit
more
longer
time.
This
is
more
as
to
what
are
the
analysis
as
well
as
we
need
to
update
space
with
him.
B
E
Not
a
specific
matrix,
I
don't
think
very
long
time
than
he
already
has,
so
this
is
more
to
see
what
are
the
different
test
scenarios
that
you
can
execute
that
we
need
to
execute.
A
A
Any
questions.
A
Okay,
the
do
we
have
a
representative
from
the
infrastructure.
Jerry
is
here
right.
Maybe
I
will
localize
for
the
infrastructure
update
the
phase
four
production
rollout.
We
are
prepared
old,
imrs
for
app
and
under
review.
So
that's
the
part
of
the
phase
for
production
go
out
and
then
the
dr
testing
preparation.
A
We
have
the
50k
environment
or
reference
architecture
created
in
gcp,
and
the
next
task
is
to
create
the
database
layer
then
hook
up
the
database.
Decomposed
databases
with
the
50k
reference
architecture
to
carry
other
testing
in
phase
5
and
6.,
so
that
goes
along
well
looks
like
we
are
on
track.
According
to
wholesale
update
in
the
issue.
A
Okay,
then,
move
on
to
raw
out
roll
out
progress,
review
so
timeline
and
the
confidence
level
remains
unchanged.
We
are
still
projecting
may
22nd,
as
the
target
eta
of
somebody
is
trying
to
say
something.
A
Okay,
I
will
continue
and
then
our
current
timeline,
we
are
preparing
to
roll
out
phase
four
to
production.
A
And
then
yeah
that's
update
from
the
infrastructure,
the
same
thing
and
then
the
chart,
the
pro
the
burnout
charts
are
here.
We
are
seeing
a
slight
kick
out
again
for
our
open
issues.
I,
if
you
look
at
the
charts
below
that
in
that
dashboard,
all
almost
all
the
new
issues
were
created
against
a
phase.
Seven
people
are
preparing
phase,
seven
roll
out.
So
that's
that's
good.
We
get
those
issues
identified
as
early
as
possible.
So
another
bad
thing.