►
From YouTube: XAF Blazor Load Testing 1000 users
Description
Click Here to Subscribe: http://xaf.life/35
Websites:
https://xafmarin.com/
https://xari.io
https://www.xafers.training/
http://xafersweekly.com/
Facebook Group
http://xaf.life/4g
Free XAF Support Hour
https://calendly.com/xari/free-xaf-support-hour
A
Hello,
everyone
and
welcome
to
another
video
about
safe
laser
in
this
video
we're
going
to
discuss
one
of
the
most
requested,
more
polemic
and
motivated
topics
about
saf.
That
is
a
load
testing.
How
many
users
can
you
have?
And
there
is
a
lot
of
we
have
done
a
meet
up
about
it.
We
have
a
lot
of
content,
a
hotel,
linux
load
testing
as
well.
So
I
we
came
across
this
service
as
you
load
testing,
and
actually,
if
you
see
it's
really
new,
it's
just
from
may
of
this
year-
and
this
is
still
in
preview.
A
So
all
the
results
are
still
again
something
that
they
are
working
on,
but
I
think
that
is
a
really
interesting
service.
So
basically,
here
they
are
using
the
geometer
to
do
load
testing
and
you
can
see
here
how
it
works
and
you
can
see
the
percentage
and
so
on.
But
the
great
thing
is
the
simplicity,
so
you
can
add
your
own
geometry
scripts
and
everything,
but
if
you
use
food
and
url,
they
create
a
script
for
you
and
test
the
scale
and
give
you
a
lot
of
insight
in
the
metric.
A
So
basically,
right
here
is
the
quick
start,
and
you
can
see
here
how
you
create
a
load
testing
resource
and
how
you
configure
it,
and
how
do
you
put
the
metrics
that
you
are
interested
in
and
so
on?
So
for
this
a
test,
we
actually
have
a
blazer
application.
Login.
Actually,
of
course,
a
just
a
simple
blazer
server
one
and
we
have
a
shop.
The
shaft
is
a
simple
one
as
well,
just
a
domain
object
with
two
records.
A
So,
besides
that
we
are
only
focusing
on
the
part
of
the
app
service
and
this
actual
load
testing
preview
service,
you
can
do
it
for
a
queue
for
sql
database.
We
definitely
have
an
sql
database
that
is
serverless.
So
if
a
scaling
on
demand,
that's
basically
what
it
is
and
right
here
if
we
go
back
to
our
let's
go
to
our
test.
A
A
Let's
leave
it
running,
you
can
configure
what
is
the
name
of
your
test?
What
is
the
the?
If
you
see
here?
This
is
the
script.
What
is
the
parameter?
We
have
the
url
that
we
want.
Basically,
we
put
a
four
engine
instance,
because
microsoft
recommend
250
a
thread
by
engine,
so
threads,
meaning
users,
so
250
users
by
4
engine
will
be
1000
users,
the
duration
of
the
test,
and,
basically
that's
it.
You
can
add
more
metrics
and
a
few
more
things.
Then
you
have
to
run
it
at
least
one.
A
A
I
think
that
is
putting
it
there
because
we
have
runners
several
times,
but
the
idea
here
is,
you
always
have
to
rule
at
once.
In
this
case,
you
can
see
the
number
of
users
you
can
see
the
response
times
in
the
client
side.
You
can
see
the
request
average
and
so
on.
After
that,
you
will
be
able
to
come
here
and
set
up.
What
is
the
component
that
you're
testing
okay,
blazers
load
test
in
the
sub
service,
and
when
you
do
that,
then
the
configure
metrics
will
be
enabled
and
then
you
can
see.
A
Okay,
I
want
the
response
time.
Cpu
average
memory
working
set
and
so
on
so
with
our
we've
run
on
blazer
server,
a
test
with
the
four
engines
and
250
thread
by
engine
250
user
by
4
engines
will
be
1000
users.
You
can
see
here
in
the
client
side.
The
response
time
is
like
361
milliseconds.
You
can
see
here
the
request
by
seconds
and
the
server
side
metrics,
you
can
see
the
request.
A
You
can
see
the
response
time
that
is
200
milliseconds,
something,
and
you
can
see
the
cpu
time
here
and
you
can
even
see
the
memory
23
megabyte.
But
if
you
see
let
me
go
back,
you
can
even
click
on
it
get
inside
that.
But
if
you
see,
as
the
amount
of
users
start
increasing
the
memory
it
went
up
to
628.
A
This
is
a
regular,
a
blazer
server
application.
If
you
see
here,
we
have
1
thousand
users
and
a
great
performance.
Let's
follow
that
and
now
let's
go
back
to
the
staff.
That
is
the
one
that
we
want.
So
we
did
the
first
one
that
it
was
with
the
standard
one.
That's
the
the
one
that
when
you
create
a
free
tire,
this
is
a
1.75
gigabyte
of
memory
and
only
100
total
acu,
and
then
we
did
another
one
with
the
p2v3
that
is
minimum
125.
A
A
If
you
see
the
response,
time
was
almost
11
seconds,
and
I
want
to
mention
here
that,
because
we
also
have
a
azure
sql
serverless,
I
didn't
put
in
consideration
that
the
first
time
that
you're
accessing
that
site
the
database
takes
longer
because
you
have
to
to
basically
get
get
out
of
rest
and
bite.
You
see.
This
is
the
the
response
time.
It's
a
little
a
lot
higher
and
you
can
even
see
here
the
response
time
on
the
server.
It
was
almost
10
seconds,
and
the
interesting
thing
here
is
that
you
can
even
go.
A
A
If
you
see
11.1
is
something
that
is
not
a
good
behavior,
but
if
you
click
on
it,
it
will
even
show
you
what
are
the
the
modules
that
they
think
that
outcast
and
vctc
they
analyze
the
thousand
requests,
and
they
are
the
thing
that
is
consuming
the
most
time
is
there
is
still
net
call
module,
so
basically
that's
the
the
place
or
the
the
the
core.
The
expert
on
that
call,
because
every
player
applications
we
know
say,
is
a
h200
page.
A
Now,
if
we
go
back
to
our
other
test
and
let's
select,
we
have
a
couple
more,
but
in
this
one
we
were
just
still
learning
I
put
here
500
by
engine
instead
of
instead
of
250
by
engine
like
microsoft
recommend.
But
this
last
one,
let's
see
you
see
the
response.
Time
is
1.25
seconds,
one
thousand
for
concurrent
user.
A
At
the
same
time,
we
have
like
a
lot
of
requests
by
second,
and
if
you
see
here
our
response
time
on
the
server
side
is
968
milliseconds,
but
I
think
that
is
a
really
reason
and
for
cpu
time
as
we
scroll
down
and
our
average
more
working
set.
So
if
you
see
the
memory
also
start
going
up
as
you
get
more
and
more
users
now,
let's
close
here-
and
let's
do
the
same
thing
here-
if
we
click
here,
we
can
see
more
information
about
the
the
server.
A
A
We
can
see
here,
I
think
I
think
this
is
one
of
the
tests,
where
I
put
more
thread
by
ending
that
the
recommended
amount
by
the
by
microsoft
now.
Another
really
neat
thing
is
that
you
can
compare
them,
so
you
can
select
all
of
them.
If
you
see
this
one
fail
and
you
can
compare
and
see
the
difference
between
between
them.
A
And
you
can
see
this
one
that
is
really
high
is
the
one
that
actually
has
only
1.75
gigabyte
of
memory,
and
I
think
that
this
was
not
even
the
issue
here.
It
was
the
cpu
that
it
has
this
100
total
hdu.
You
can
see
again
virtual
user
here.
You
can
actually
uncheck
and
check
all
the
tests
to
see
what's
going
on.
So
this
is
just
we
are
starting
to
play
with
it.
We
just
wanted
to
put
it
over
there
in
case
somebody
else
in
the
community.
A
They
want
to
play
with
it
or
actually
the
same
their
express
team,
because
one
thing
that
I
have
to
mention
this
actual
load
test
in
service
is
not
great,
so
they
have
a
pricing
that
you
can
look
it
up
online
and,
depending
on
their
the
amount
of
engines
that
you're
using
the
amount
of
users
that
you
are
adding,
it
will
have
a
small
cost,
but
as
much
use,
as
you
add,
as
much
engine
ui.
Of
course,
that
cost
will
be
increasing
so
where
you're
testing
with
it.
A
I
do
believe
that
if
we
check
the
results
from
the
blazer
one
that
was
300
milliseconds
and
the
staff
that
was
941
milliseconds,
I
think
that
is
really
promising,
but
we're
going
to
be
able
to
accomplish
with
just
one
server,
not
load,
balancing,
not
a
scaling
out
just
scaling
up
with
essentially
so
that
would
be
my
video
for
today.
Okay,
if
you
have
any
input.
B
A
B
We
behave
in
one
year
or
in
three
years
four
years,
because
you
know
that
the
most
common
cases
that
we
have
in
the
office
is
that
my
application
was
working
well,
the
third
day,
but
it's
been
like
one
year
and
it's
not
working
anymore.
So
you
with
a
tool
like
this,
you
can
foretell
how
it's
going
to
behave
in
the
future
when
your
audience
grows.
A
We
are
actually
starting
to
understand
what
all
these
comparison
metrics,
how
all
these
things
are
tied
together
so
and
right
now
we
are
only
seeing
just
the
app
service
we
want
to
see
the
type
also
do
it
load
test
into
the
database,
so
we
want
to
basically
start
now
using
the
service
that
gives
you
a
lot
of
power
to
see
how
we
can
give
you
guys
more
numbers.
I
wanted
to
put
out
there
if
you
guys
have
a
the
opportunity
in
your
company
and
you're
just
do
some
tests
as
well
and
share
it
with
us.