►
From YouTube: 2021 07 07 EMEA Sharding Group Sync
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
A
Yeah,
I
I
could.
My
microphone
was
muting
itself.
A
C
B
B
C
C
The
request
from
eric
at
the
original
request
that
was
communicated
us
was:
what
can
we
do
to
bring
the
timeline
into
october?
That
request
has
been
revised
to
say
what
can
we
do
to
bring
the
timeline
in
and
he
asked
for
a
blank
check
proposal,
meaning
without
any
limitations
on
people
staffing.
Anything
like
that.
C
How
could
we
bring
the
timeline
in
so
the
approach
I
took
in
this
case
was
just
to
lay
out
the
work,
the
known
things
that
we're
working
on
put
them
in
a
timeline
and
bring
them
forward
again
without
restriction
of
thinking
like
okay.
Well,
there's
only
one
jose,
so
he
can't
really
do
multiple
things
at
once,
so
removing
that
restriction
and
just
talking
focusing
on
the
work,
I've
gotten
some
feedback
from
a
few
folks.
I
think
fabian
you've
seen
this.
I
don't
know
if
you've
commented
on
this
at
all.
C
Dylan
and
tong
both
gave
some
ideas
and
filled
in
a
couple
gaps
where
we
didn't
have
some
work,
and
since
then,
we've
identified
a
couple
areas
where
again
going
with
the
blank
check
methodology,
we
could
bring
some
things
forward
so,
like
distribution,
it
was
originally
scheduled
for
a
month
or
two
from
now
based
on
current
work,
but
in
the
blank
check
world
they
could
start
doing
it
now,
because
they'd
have
unlimited
people
to
be
able
to
work
on
this
stuff.
C
The
these
three
things
together
use
an
example
below,
in
reality
with
the
team
size
that
we
have
and
the
people
working
on
it.
These
would
more
likely
be
serial,
but
in
a
blank
check
world
we
could
do
these
all
in
parallel,
because
we'd
have
an
unlimited
number
of
urics,
let's
say
to
work
on
database
stuff
to
discover
and
mitigate
like
cross,
joins,
remove
foreign
keys,
etc.
C
So
this
is
the
approach
I'm
I've
taken
on
this
one
and
it
gets
us
around
a
november
timeline
and
feedback
is
welcome
and
encouraged.
If
anybody
sees
any
gaps
on
things
that
we
haven't
put
in
here
for
work,
please
add
them
and
feel
free
to
shuffle
around
dependencies
or
bring
things
forward
and
just
comment
on
what
you
changed
so
so
that
I
know
what
was
changed
any
questions
on
this
and
please
don't
look
at
this
as
hard
and
fast
commitments
on
anything.
This
is
really
just
brainstorming.
B
B
That
can
create
inefficiencies
just
with
coordination,
but
that's
that's
something
to
be
figured
out
when
we,
when
we
get
to
that
point,
but
it's
I
think
this
is
where
these
charts
actually
sometimes
are
nice,
because
they
they
make
this
more
apparent.
So
thanks
for
doing
it.
C
Yeah
to
your
point,
that's
kind
of
like
the
second
stage,
like
all
right.
If
we
all
agree
like
again
in
a
blank
check
world,
we
could
bring
all
these
things
forward
and
have
all
this
work
done
in
parallel,
and
then
you
start
applying
reality
to
it.
That's
when
things
start
slipping
off
like
oh,
we
don't
have
11
fully
dedicated
teams
or
whatever
that
normal
was
that
we
number
was
that
we
have
going
in
parallel,
what
makes
the
most
sense
to
push
back
or
apply
teams
to
etc.
D
D
D
Everyone
is
more
than
welcome
to
participate
the
point
of
the
network,
something
we'll
be
discussing
here
a
bit
more
because
we
have
a
vpc,
but
we
need
to
be
extremely
careful
with
the
english
and
negative
traffic,
something
I
wanted
to
be
sure,
200
percent.
Before
we
proceed,
you
do
not
have
like
any
web
hooks
or
any
kind
of
communication
with
exterior
generating
trouble,
and
there
is
more
updates
here.
You
need
to
read
more
but
yeah.
D
I'm
saying
this.
Why?
Last
time
I
have
been
for
two
or
three
months
working
in
this
benchmark
environment
and,
unfortunately,
a
srs.
They
were
not
able
to
set
up
properties
properly,
because
some
problems
in
environment
or
difficulties
they
found
out.
I
found
out
the
solution
with
the
with
nick
about
net
data
that
was
pretty
nice
to
gather
basic
methods
from
the
os.
I
have
some
examples
in
the
issue.
D
Okay
and
other
steps
here
is
like
how
to
provision
the
environment
itself.
I
want
to
document
it
it's
straightforward
from
there
or
following
chef,
but
still
I
think
it's
good
to
have
this
clear
and
how
to
reset
it
as
well
in
case
every
time
that
we
do
a
test.
We
want
to
go
back
to
the
scratch
to
execute
again
a
test
with
a
different
change
in
neurological
different
steps.
We
have
these
documentaries
and
basically,
I
listed
as
well
the
two
tests
that
we
are
initially
thinking
about,
of
course,
can
be
more
or
more
changes
there.
D
Everybody
spoke
with
dylan
and
the
team
today
earlier,
for
what
I
see
as
well.
Do
you
stop
sharing
it?
There
was
a
question
from.
D
B
Sorry,
you
say:
are
you
reading
my
question?
Yes,
okay,
yeah,
I
can
explain
it's
like.
I
think
we
created
in
our
issue
tracker.
B
This
sort
of
we
have
to
set
up
a
a
testing
environment
to
to
test
it
and
then
there's
also
an
epic
for
sort
of
more
benchmark,
related
tasks
right
as
in
you
know,
things
that
they
may
want
to
evaluate.
B
I
was
just
wondering
if
we
can
at
least
close
this
one-
the
first
issue
here,
which
is
the
set
up
a
sharding
environment,
one
because
that
is
clearly
captured
in
the
epic
that
you're
you
created.
So
what
I
would
suggest
yeah.
B
D
B
Closed
as
well,
because
we
we
are
done,
we
are
done
with
the
poc
stuff.
I
think
essentially
right.
It's
like
we're
going
to
move
forward
with
this,
so
I
think
we
can.
D
We
can
whatever
you
need
to
test.
I
need
you
to
feel
what
we
need
to
do
me
and
sres
in
infrastructure.
We
need
still
to
provision
one
box
there
to
be
able
to
roll
out
this
have
a
look
on
the
network,
but
I
think
we're
pretty
done
on
this,
because,
unfortunately,
the
pc
environment
is
not
ready,
yet
they
found
more
problems
than
because
the
the
problem
here
is
like
did
it
from
the
scratch
and
they
tried
to
reorganize
the
more
components,
and
this
got
more
complex.
B
Unfortunately,
great
thanks,
I
will
close
these
issues
then,
because
then
we
have
no
duplication
and
we
can
say
infrastructure
is
now
tracking
this
over
here,
and
that
makes
sense.
Would
you
agree
craig.
C
I
was
just
gonna
say:
should
we
keep
them
open
and
just
say
tracked
on
infrastructure
issue
over
here?
That's
how
I've
seen
it
done
before,
but
that's
just
so
that
we
keep
them
visible
on
our
board,
so
we
don't
lose
track
of
them,
but
I
don't
have
a
strong
opinion
if
you
want
to
close
them
and
say
tracking
over
here.
It's
fine
too.
A
B
Yeah,
I
think
that
can
that
can
definitely
be
closed.
Okay,
then
I'll,
okay,
I
like
the
idea
from
from
craig
and
I'll
just
leave
a
note
in
there
saying
this
work.
We
we
have
this
for
tracking
purposes,
but
it's
going
to
happen
over
here.
So
people
know
what's
what's
going
on.
B
No
sorry,
sorry,
this
is
me,
I'm
not
trying
to
make
it
more
complicated,
I'll
share
my
screen.
Okay,
so
we
you
have
created,
you
did
create
this
one
here,
nope
one!
Second,
this
one
here
we
leave
this.
This
is
your
new
playground,
where
you're
going
to
do
all
of
the
work
related
to
the
benchmarking
environments.
B
We
a
while
ago,
created
this
epic
here
this
issue
here,
setting
up
a
sharding
environment
which
is
essentially
describing
exactly
what
you're
doing
now.
A
B
My
question
is:
can
we
close
this
or
not,
and
I
think
craig
suggested
to
maybe
leave
it
open
but
provide
a
link
to
your
epic
and
say
this
is
only
for
tracking
purposes.
You
know
the
work
is
happening
happening
over
here,
so
we
don't
lose
track
of
it
and
I'll
do
the
same
with
this
epic
here,
which
is
sort
of
testing
on
production
like
data.
This
was
the
like
our
way
of
saying
hey.
B
D
As
you
prefer,
but
if
you
see
here,
for
example,
you
are
mentioning
zfs,
we
are
using
gcs's
disk
snapshots.
This
is
slightly
different
in
the
previous
epic.
I
would
strongly
recommend
that
we
close
the
epic,
the
four
seven
one
is
not
wrong
because,
like
the
tasks
that
are
attempting
to
do
that
are
already
covered
here,
look
this.
B
Yeah
yeah,
this
is
this-
is
why
I'm
highlighting
it.
I
want
to
make
sure
we
don't
have
like
15
things
saying
the
same
thing
and
nobody
knows
where
we
where
we
are
at
okay,
so
this
is
done
I'll,
remove
all
of
that
I'll
clean
that
up
after
the
call,
and
then
that
will
be
fine.
A
E
What
sorry
I
missed
the
first
10
minutes,
but
what
was
discussed
about
the
blank
check
proposal?
Any
anything
any
highlights.
E
D
Yes,
actually,
the
epic,
where
I
designed
it
like
what
we
need
to
do
to
adapt
or
benchmarking
environment
that
nowadays
has
a
good
is
equal
to
production.
That's
in
the
database
level
and
we're
using
the
emitter
to
generate
the
traffic,
and
we
could
test
there
or
approaches
for
the
sharding
proposal.
D
E
Thank
you
thank
you,
and
also
since
people
are
here
the
reason
I
was
later
because
we
were
working
on
this
blocker,
the
production
data
blocker,
which
you
created
jose
that
issue
infrastructure
issue.
So
we
are
trying
to
answer
the
questions
to
eric,
and
hopefully
we
get
support
to
move
the
needle.