►
From YouTube: 2023-05-11 Scalability Team Demo
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
Probably
have
some
nice
thanks
for
recording
just
some
probably
shot
brainstorming,
just
to
gather
some
ideas,
because
this
kind
of
a
little
bit
quirky
on
how
it
works.
So
let
me
just
copy
the
item.
A
We
want
to
have
a
mechanism
to
differ
certain
psychic
jobs
in
the
case
of
where
there's
a
Runway
worker
that
uses
too
much
resources
in
the
database,
for
example.
So
you
don't
have
a
mechanism
to
immediately
kind
of
stop
this
worker
or
defer
them
to
run
in
another
time.
So
my
idea
is
to
it
is
brainstorming
previous
robbing
session
with
syllabus,
also
so
with
the
feature
flag.
So
we
can
introduced
a
new
actor
type
of
worker,
so
we
currently
have
those
users
groups
repository
and
we
can
extend
with
a
worker.
A
A
A
A
They
turn
it
off
until
then,
Sr
return
it
on,
for
example,
yep.
So
this
is
working,
but
but
up
there's
another
additional
feature
that
probably
they
won't
want,
as
well
from
an
Ops
point
of
view,
is
to
do
some
kind
of
rate
limiting
so
throttling
the
jobs
yeah.
So
so,
with
this
approach,
it
doesn't
work
that
well
for
to
in
order
to
cater
for
that
rate,
limiting
because
initially
I
was
thinking.
A
We
could
use
this
percentage
of
time
feature
from
The
Flipper
itself,
but
then
it
doesn't
work
well
together
with
the
actor
type
because
they
are
like
a
different
in
a
different
gate.
So
if
you
turn
on
the
specific
actor
or
for
that
worker,
and
then
you
turn
on
also
the
percentage
of
time.
What
happens
is
that
for
that
particular
worker,
it
will
be
deferred
100,
but
for
the
other
workers,
it's
gonna
follow
the
percentage
of
time
Randomness
logic
yeah,
so
I
was
thinking
of.
We
could
kind
of
hack
it
a
little
bit
by
doing.
B
We
can
find
a
dynamic
feature
Flags
if
you
underscore
the
the
name
of
the
worker
or
something,
then
you
do.
A
B
A
Yeah,
so
it's
like,
you
always
have
four
car,
so
this
is
what
the
Swiffer
ID
would
look
like
in
the
end,
but
yeah,
as
you
said,
this
is
dynamic.
So
if
you
want
to
check
whether
that
worker
has
this
feature
flag,
it's
not
a
simple
feature.enabled
call.
You're
gonna
have
to
iterate
over
all
the
actors
value
because
you
would.
You
can
have
like
multiple
values
right.
At
the
same
time,.
B
Yeah
I
was
thinking
more
like
chatops
run,
features,
Set
rate
limits,
rate
limit,
sidekick,
now
rate
limit,
authorized
projects,
worker.
B
A
C
For
yeah
you
can
you
can
now
you
try
before
also
I
I
was
talking
about
multi-story
storages
like
it's,
not
Dynamic,
the
the
future
of
that
string
is
interpolated.
So
if
it's
interpolated,
then
you
have
to
the
definition
is
to
me.
No,
if
there's
a
definition,
if
the
usage
must
be
must
be
found
in
the
code
base.
But
you
just
know
that
if
there
is
no
definition,
then
you
can
technically
use
whatever
features
that
you
want
and
I
think.