►
From YouTube: Community Engineering Hangouts - BulkApi examples
Description
Community Engineering Hangouts.
The aim of these hangouts is to update the community on all our progress and demo some new tools and features. For this live stream we have the following agenda.
1. News and updates from the Community Engineering team,
2. Real world examples of how to use the new BulkAPI,
4. Live Q&A section,
During this hangout we will be showing you some of the powerful new BulkAPI capabilities and hopefully inspiring you to include these in your projects.
Using the postman examples https://github.com/nuzil/magento-postman we will step through how to get up and running with the BulkAPI.
Feel free to join in, comment and ask questions. The aim of these hangouts is to provide a platform for Magento to give the community regular updates but also for the community to give feedback to Magento.
For any more information feel free to reach us at engcom@magento.com
A
A
So
that
is
the
aim
for
today,
but
first
I'm
gonna
just
do
an
update
from
last
month,
with
a
few
of
our
set,
and
so
last
month
we
had
661
pull
requests
and
created.
We
processed
and
839
so
we're
processing
some
from
a
previous
month
and
with
72
percent
acceptance
rate,
which
is
fantastic,
and
we
had
200
over
200
contributors
overall,
which
is
also
pretty
great,
and
so
it's
great
to
have
everyone
and
yeah
looking
forward
to
it.
A
A
B
B
B
B
I've
seen
you
can
multiply
balls,
they
using
they're
a
bit
in
queue,
so
you
have
to
have
very
bit
imp
you
installed
and
to
enable
the
riveter
queue
for
your
Magento
instance.
You
just
go
into
a
bit
it
C
environment,
HP
file-
and
you
paste
me
here
this
part
of
the
code
which
already
prepared
before
where
you
turn
that
the
queue
and
that's
the
connection
name
and
then
you
have
like
base
parameters
which
is
hotspot
user
passport
and
virtual
host.
B
Those
parameters
which
I
feel
here
now:
those
user
name
host
password
and
appall
they're
coming
like
default,
one
if
you'll
install
the
ribbon
mq
on
your
arm.
So
that's
the
first
step
after
that,
so
I
I
will
use
ribbon
in
view
interface
to
show
you
the
result
and
the
status.
And
if
you
go
into
your
evident
you
interface
to
the
queues
you
will
see
here.
This
queue
it's
created
by
Magento
and
at
these
points
very
important.
B
B
B
C
B
A
B
Devices
today,
Terry
didn't
fire
good
yep,
that's
one
so,
and
yeah
I
was
starting
from
database
park.
Api
and
or
syncope
is
basically
Magento's
in
preparation
operations
module.
It
will
create
new
tables,
which
is
a
gentle
bulk
which
contain
all
the
operations
that
were
called.
It
will
be
filled
during
our
demo.
You
will
see
and
Magento
operation,
which
contains
a
single
operation
of
each
part
per
your
request,
so
I
would
propose
in
let's
go
through
so
we
I
prepared
here
several
get
calls
which
are
not
a
single
bulk.
B
B
B
B
B
First
of
all,
what
is
difference
between
use
or
rest
in
the
bulk?
Then
you
have
those
two
prefixes
here
is
a
symbolic
and
if
you
kill
here
at
fault,
there
rest
will
baby
Goudas
neutron
OC,
but
it
will
expect
the
same
body
as
standard
modular,
gayness
and
bulk
telling
to
Magento
that
this
request
political
will
be
executed
in
bulk.
So
it's
expected
a
little
bit
another
body,
so
the
standard
body,
basically
is
your
product
object.
B
Then
CEO
standard
modular
API
try
to
do
it
smaller,
but
it's
done
as
Magento
API
and
if
you're
talking
about
bulk,
we
just
like
wrap
it
into
the
area
and
yeah
and
be
transferring
the
multiple
items
just
one
by
another.
Here-
and
here
you
see,
like
one
body-
was
basically
51
products
at
the
same
time
and
the
URL
will
stays
the
same.
B
So
nothing
change
from
the
standard
rest
and,
if
I'll
send
it
to
Magento,
which
will
take
some
time
to
a
center
and
then
it
will
return
back
the
basically
the
the
statuses
at
this
point.
Magenta
is
not
proceeding
the
products
directly,
so
it
just
accepted
the
all
those
requests
and
put
them
in
a
queue
and
also
if
we
will
go
to
the
tables
of
show
you
before.
That's
our
operation
table.
That's
all
our
requests.
They.
A
C
B
Go
to
the
previous
table
also,
that's
our
ball,
which
is
one
request
which
has
a
topic
name
defined
and
it's
contained.
Basically,
this
t51
operation
count
operation,
yeah
and
that's
all
topic
names
topic
names
are
generated
in
magenta
automatically
I
mean
generated
from
the
web
api,
but
based
on
the
web
api
xml.
B
That's
basically
the
service
contract
of
the
each
request,
which
has
just
like
a
scene
prefix
in
the
before,
and
the
type
of
request
in
the
end
like
post
put
or
to
delete
and
that's
basically
the
service
contract
itself.
Just
well
slashes
replaces
adults
and
it's
lower
taste.
This
happen
and
auto-generate
is
all
this
mean
when
you
will
have
your
custom
module
installed,
customer
B,
I,
developed
yeah.
It's
also
will
be
available
to
execute
in
a
Cinco
Parkway.
You
don't
need
to
do
anything
special
from
it
yeah
and
how
basically
to
execute
today's
smart.
B
We
will
go
to
our
monitor
installation
and
if
we
will
do
in
Magento
you
you
will
see
there
is
an
asset
of
the
queue
operations
which
are
available.
It's
again
a
consumers
list
and
the
static
consumer
Magento
Community
Edition
has
a
button
to
open
source.
Sorry,
sorry
I've,
just
really
will
have
only
one
consumers
out
of
box.
It's
basically
consumer
force
in
corporations
and
yeah
I
mean
if
using
much
of
the
commands.
B
B
C
B
B
Let's
go
yeah
and
what
I
also
want
to
show
I
mean
I
showed
you
that
that's
basically
the
database
and
tensor
result,
but
you
not
always
have
a
totally
sexist
or
you
don't
want
to
use
it.
So
then
you
can
use
this
ID,
which
is
our
key
ID.
It's
a
same
ID.
We
will
go
back
here
when
you
execute
the
previous
request
and
what
you
can
do.
You
can
get
a
status
of
it.
B
B
If
you
don't
want
to
get
the
like
full
body-
and
you
won't
do
it
faster
here-
is
another
call
which
called
just
status,
which
will
also
only
retrieve
the
message
and
the
stairs
yep.
That's
basically
it
it
couldn't
break
it.
So
yeah,
that's
our
response,
any
as
you
can
see.
We
have
51
products
in
magenta.
B
B
Just
will
clone
some
windows
here,
so
you
can
run
the
multiple
consumers
which
will
speed
up
the
process,
for
you,
I
guess
that's
too
much,
so
we
have
here
five
five
consumers
which
I
can
run
and
they
will
all
basically
work.
That's
kind
of
you
have
five
workers
who
is
working
for
the
same
queue
and
they
will
all
listen
for
it
and
first
one
get
the
message
start
to
executed
and
then
like
this
message,.
B
B
B
Okay,
then
I
was
here
to
be
wrong
because
I
waited
before
before
and
the
consumer,
so
what
I
will
do
now
I'll
do
this?
One
I
will
cancel
them
all
and
I
will
leave
only
one
here,
working
this
edit
and
now
I
always
start
again
and
what
we
have.
Currently
we
have
the
dis
previous
request,
which
we
started
to
execute.
Our
system
received
like
1712
and
I
was
25,
so
it's
took
us
14
seconds
to
execute
and
if
I
will
check
this
one,
it
was
from
59
started.
Let's
try
running,
it
was
one
consumer.
B
B
B
So
yeah,
that's,
basically
you
always
have
some
threshold
and
you
have
to
be.
You
have
to
take
care
about
your
system
performance
about
your
resources,
so
we
have
be
careful
with
that.
Also,
my
general
acceptance
is
the
problems
with
a
deadlocks.
If
you
run
and
too
many
requests
at
the
same
time
always
take
care
about
your
system
load
like
how
many
customers
of
their
and
what
does
it
do
you
know
how
many
elements
and
then
what
does
it?
Do
we
on
our
project
basically
currently
running
some
tests.
C
B
Provided
by
magenta
and
I
hope
in
you
we'll
get
the
test
results,
then
we
can
tell
you
what
is
perfect
amount
of
the
request
you
you
can
run
or
consumers
you
can
run.
So
that
was
the
simple
products
and,
as
Thomas
time
is
going,
I
will
start
them
with
basically
configurable
products
before
that.
I
can
show
you.
So
that's
basically
our
category
tree
currently
and
what
I
want
to
do
before
in
such
an
import.
I
want
to
create
some
categories.
So
again,
request
is
the
same.
B
B
I
charge
like
to
make
this
process
kind
of
categories
as
simple
as
possible
like
to
use
their
all
functionality
of
BOM,
providing
or
there's
two
a
problem.
If
you
only
make
the
complex
three
with
a
child,
you
have
to
do
it
in
several
steps,
because
we
have
to
know
that
parenting,
you
of
your
child,
but
in
any
case,
given
its
an
example
like
those
Kelly,
was
a
credit.
I
made
one
of
them
disabled,
just
sure
that
all
working
correctly,
but
here
they
are,
and
let's
switch
to
create
a
configurable
product
that
was
planned
for
today.
B
Okay,
that's
our
body,
so
what
is
lies
in
Bulgaria
I
can
do
preparation
of
the
greater
country
group
product
in
one
call:
I,
don't
need
it
separately,
so
that
is
list
of
all
products.
We
need
for
the
to
be
stricken
fuel
products
with
two
custom
attributes,
one
product
with
two
attributes
link
and
two
products.
With
one
attributes,
configurable
attribute
to
confirm
phone
with
API,
you
need
to
execute
more
than
one
call,
and
in
this
example,
we
have
run
until
it's
not
taking
the
time
to
execute
it.
But
I
created
configurable
products.
A
B
B
B
Then
you
will
have
much
more
like
flexibility
to
reduce
the
amount
of
calls.
So
that's
what
we
are
doing
next
yeah
here
is
our
is
our
request.
We
have
four
because
we
have
wanted
to
build
with
two
options
into
one
product
options
and
two
products
with
one
option
which
it's
for
and
then
a
separate
call
willing
them
willing
them
it
between
each
other.
B
B
With
the
custom
attributes
and
that's
one
bond-
and
here
is
our
two
and
over
smoothly-
and
you
take
too
much
time
and
in
mine-
calls
I
use
quite
basic
bodies
of
the
request
object
here.
It's
quite
basically
I,
don't
have
any
matrix.
If
you
edge
like
gallery
images,
it
will
time
of
processing
will
be
slower
and
if
you
learn
some
custom
attributes
so
use
some
extension
of
the
extension
attributes
or
you
will
use
some
custom
stock
management,
so
tech
calls
will
exactly
with
is
a
bit
longer.
B
But
what
I
like
in
this
is
all
this
approach
that
you
basically
don't
really
care
when
it
is
acute
it
because
request
is
accepted,
like
super
super
fast
yeah,
and
that's
that's
basically
very
good.
As
for
me,
as
for
developer
of
the
like
connectors
between
Magento
and
unity,
for
example,
one
more
interesting
stuff
which
I
forgot
to
turn
to
explain,
follow
me
for
that
original
API
call
I
mean
if
you
look
on
on
a
usual
magenta
swagger,
the.
B
So
this
mean
you
can
execute
only
one
link
operation
for
each
call,
and
in
this
URL
you
have
to
define
the
SQ
so
there's
parameters
in
URL,
which
is
very
common
in
magenta.
It
can
do
1,
it
can
be
2
or
3,
so
the
to
do
the
parameter
when
you
have
a
path,
because
we
have
a
multiple
items
in
one
request.
B
So
what
you
have
to
do,
I
will
put
it
back:
okay,
the
parameter
which
is
defined
in
API
like
this,
you
basically
play
or
replace
and
with
it
just
happened.
Let's
end
with
the
prefix
by
and
make
in
our
case,
like
first
letter
of
the
parameter,
and
then
this
problem
user
is
carried
in
a
body.
So
usually
the
single
API
request
looks
like
this,
where
you
have
only
like
child
is
QD
because
original
schools
in
Europe,
if
you're
talking
about
bulk,
then
sq
is
coming
in
a
body
and.
B
Yeah,
it's
the
same
here
with
a
set
of
configurable
attributes
where
the
Eskimo
that
was
defined
in
the
Ural
before
is
going
to
a
body
and
yeah,
and
then
basically,
Magento
will
make
them
together
and
will
assign
to
correct
product.
The
good
example
example
of
this
one
and
what
I
wanted
to
show
you
also
there's
two
prices
of
Magento.
B
The
original
Magento
two
prices
call
has
three
parameters
inside
it's
an
probably
sq
its
customer
group,
ID
and
I
to
inform
and
it's
Kiki
I
and
its
price
and
everything.
Oh
did.
You
know
this
is
transferred
in
a
URL,
and
this
call
has
nobody
at
all
by
default
in
magenta.
So
what
what
I
did
here?
I
replace
as
I
explained
before
all
parameters
with
the
PI
prefixes
and
then
all
those
parameters
come
in
like
an
object
in
a
body.
B
B
B
B
A
C
Extras
for
some
requests:
we
we
need
to
get
bulk
status.
We
need
to
answer
allies
them
and
the
code
to
get
some
ID
idea
in
case
of
invoice
order
or
credit
memo
creation.
We
we
always
need
to
wait
until
our
pair
will
be
created,
then
check
about
status
and
service
them
and
get
order.
Id,
get
order,
item
idea
and
I
want
to
show
you
some
trick
to
make
this
course
coaching
without
waiting
and.
B
C
Take
them
and
then
use
response
in
invoice
bulk
requests
instead
of
this
I
made
some
example
as
sample
model
which
use
mass
consumer
sailors
what
he
did.
Actually,
this
mass
consumer
sales
is
method,
class,
mass
consumer
and
operation
processor,
which
operate
by
message,
key
messages
and
what
I
eat
here.
I
just
inject
order,
collection
order,
item
collection,
I,
get
message,
magenta,
encode
them
and
I
search
entity
order
ID
by
some
increment
idea.
C
C
C
C
C
So
yeah,
we
don't
need
this
one
anymore,
so
we
create
all
the
increment.
Id
extension
tribute
second,
create
new
consumer
mass
consumer
sales.
We
just
say:
listen,
another
qui,
a
sync
operation,
all
sales
and
I
created
some
publisher,
because
if
we
have
original,
if
we
will
use
original
publisher-
and
we
will
have
to
run
@q
example.
C
Consumer,
we
don't
want
to
use
because
they
don't
have
our
customer
implementation
to
find
to
found
order,
entity,
ID
or
order
item
ID.
We
we
need
to
use
only
one
consumers
so
because
of
this
reason,
I
don't
want
to
use
original
publisher
original
topology
I
also
created
a
different
exchange
and
link
it
them
to
to
the
icing
agenda
service
API,
safe
post,
which
is,
will
handle
order,
invoice
and
create
management
topics.
C
C
C
C
So
a
reason
why
I
show
you
this
instead
of
of
perform
postorder
balls
and
get
orders
and
inject
to
post
invoice
bulk
result
from
post
order,
bulk
I
used
one
by
one
and
I,
don't
need
to
wait
before
order
bulk
requests.
You'll
finish
it
I
I
will
not
wait
until
this
operation.
If
example,
you
have
thousands
of
orders,
I
don't
need
to
wait.
I
just
can
perform
this
free
calls
and
go
home
as
ever.
C
B
Cool,
thank
you
Alex.
It
was
really
cool,
yeah,
the
stuff
which
I
explained
for
you.
When
you
making
the
chain
calls,
you
always
have
to
wait
for
responses
and
to
read
those
responses
and
there's
a
great
example
of
the
way
how
you
can
use
a
synchronous
API
when
you
not
waiting
for
responses,
and
you
just
run
all
course
you
have
to
the
queue
then
hopeful,
I
guess
this
also
can
be
applied
like
to
configure
all
products
for
a
floor
which
I'll
just
create
it.
Where
you
just
put
it.
A
We
have
some
time
range
to
do
now.
Is
we've
got
a
couple
of
questions
in
in
the
chat?
So
maybe
we
start
with
those
questions
and
then
we
can
maybe
dive
into
a
bit
more
if
those
questions
bring
anything
up.
So
the
first
question
I
need
at
any
point,
you
have
more
questions,
just
open
the
chat
and
we
will
get
to
them.
So
first
is
from
Nick
and
he
asks
about
the
scope
of
the
bulk
API,
so
I'm
guessing
this
means
what
what
is
included
in
terms
of
what
can
you
do
out
of
the
box?
A
B
So
basically,
yeah
I
mean
it's
not
kind
of
development
where
we
define
him
like
which
endpoints
it's
after
execute
it's
working
on
a
top
of
the
API
and
it's
just
taking
all
requests
which
are
coming
to
the
standard
service
context
and
convert
them
to
bulk
automatically.
If
you
ask
them
like,
please
make
me
back
out
of
it,
so
we
don't
need
to
develop
basically
anything
just
just
just
use
it
cool.
B
B
A
B
B
There
are
hisses
vaguer
for
for
synchronous,
API,
which
is
available
with
magenta,
also
Auto
box,
just
with
your
standard
swagger
just
add
like
new
parameter
in
the
URL,
which
called
type
I
think
we
can
also
the
next
poster
to
me.
Yeah
in
description
of
all
the
recording
will
do
better
yeah,
that's
basically
first
first
step
and
then
then
just
go
go
ahead.
Gentle
dev
don'ts
also
has
nice
articles
about
the
park.
Api.
C
A
D
B
Benefit
for
me
that
we
have
a
project
with
running
the
riveting.
You
are
on
already
running
and,
like
a
couple
of
months
ago
and
I
checked
the
statistic
like
how
many
requests
we
had
per
day
coming
to
Magento,
and
there
was
a
couple
of
days
when
we
had
up
to
1
million
API
requests
coming
in
too
much
until
since
it
was
like
800,000
and
the
most
important
for
me
here.
That
I
had
no
idea
about
that.
That
I
can
just
have
a
system
with
Charlene
stable
I
had
no
time
times.
B
I
have
no
complaints
that
the
system
Brian
slow
or
some
data
missing
it.
Just
just
those
two
days
weeks
just
went
through
and
I
didn't
know
about
them,
and
that's
basically
the
most
important
for
me,
but
Mark,
API
and
I
can
make
it
running
and
yeah
and
I'm
relaxed
I
have
nothing
to
worry
about
that.
It
will
overload
the
system
with
was
a
request.
Yeah
awesome.
A
A
D
B
B
Like
use
cases
from
another
project,
for
example,
we
had
several
use
cases
from
our
site
project
which
are
slack
for
one
or
another
improvement.
If
you
need
some
another
queue
system
running,
we
can
check
it.
How
much
effort
we
need
to
integrate
it,
how
easy
that
and
maybe
make
some
integration
for
it.
One
note
to
your
question
that
magenta
khan
has
you
systems
its
revenue
and
database
database
like
not
require
any
additional
software,
and
you
can
just
use
the
database
as
a
cue
processor
park.
B
Api
is
not
supporting
the
database
processing
to
have
a
database
processing.
You
need
to
build
another
consumer
and
as
a
publisher,
so
like
another
processor
which
will
publish
the
messages
and
another
which
will
read
it
in
our
project.
We
have
this
in
plans.
We
basically
we
just
looking
for
the
for
the
contributors
on
this
point,
because
we
have
so
many
issues
that
we
can
install
them
all
at
the
same
time.
Yes,
so
if
somebody
will
be
interested
to
support
us
here,
yeah
the
differently,
okay,
cool.
C
A
B
We
have
an
in-depth
article,
which
called
Balkan
points
which
will
describe
the
URL
structure
which,
which
requests
I
accept
it
and
how
to
convert,
parameter
and
embody
parameter
school
yeah.
You
can
definitely
have
a
look
there
if
you
missin
some
information.
Also
good
point
to
the
people
who
are
listening
will
watch
it
just
drop
me
a
message
to
drop
medicine,
bark
API.
We
can
write
additional
death
dogs
if
it's
required
for
their
people,
so
that's
quite
easily
that
something
we
can
easily
do
awesome
cool.
A
I
think
that
covers
all
of
my
questions
again,
if
anyone's
listening
and
has
any
questions
feel
free
to
reach
out
to
us.
We
have
about
10
minutes
left
but
and
I
know.
I
actually
have
one
more
thing
that
you
would
like
to,
and
if
you
have
time,
if
you
think
you
can
fill
it
in
that
time,
I
can
try.
Then
we
can
do
it
before
we
do
that,
though,
I
would
like
to
just
highlight
that
we
are
coming
up
to
imagine
so
imagine
is
coming
up
in
a
week
next
Saturday
and
Sunday.
A
But
we
would
like
you
to
register
so
we
can
know
about
catering
options
and
stuff,
so
we
know
how
much
we
can
prepare
as
best
as
that.
If
you
have
any
questions
about
anything
you've
seen
and
feel
free
to
reach
out
to
me
on
Twitter
or,
however,
in
slack
whatever
my
twitter
is
at
Manistee
and
there's
also
the
community
engineering
twitter
and
so
feel
free
to
reach
out
that
way.
If
you
have
any
questions
at
any
point,
reach
out
that
way,
and
then
god
tomorrow
I
assume,
no
one
will
be
watching
this.
A
Who
is
from
India,
because
it
is
quite
late
right
now,
but
at
tomorrow
there
is
a
distributor
contribution
day
across
the
whole
of
India,
which
is
amazing
to
see
Vijay
was
in
the
call
earlier
because
he's
currently
in
America
and
but
that
is
super
exciting
to
see
and
I'm
excited
to
see
what
comes
out
of
that
last
year's
event
was
a
great
success,
yeah
other
than
that
yeah.
Let's,
let's
see
what
we
can.
D
B
Now
it
is
I
hope
so
so
yeah
I
will
take
over
this.
One
I
have
one
more
as
I
told
before
some
tricks,
how
other
you
can
use
some
option
to
buy
PP
I
can't
imagine,
tomography
I
send
in
all
requests
which
you
will
execute
to
the
one
cube,
which
is
a
sync
operation:
all
and
yeah.
You
can
run
multiple
consumer
on
the
same
cube,
but
what
you
can
also
do
you
can
split
your
Magento
Park
API
to
be
executed
like
in
different
queues
also
and
by
different
consumers.
So,
basically
we
use
the
Lord.
B
C
B
B
What
I
will
do
I
will
remove
this
one,
which
is
original
one,
just
as
Alex
already
explained,
Della's
Alex,
that
if
you
have
them
at
the
same
time
running
a
sync
operation,
all
will
listen
for
all
topics
whatever
they
are.
This
meaningful
that
so,
if
I
will
leave
this,
enable
that
will
be
that
will
work
like
I
have
to
consumers
running
at
the
same
time,
because,
if
possible,
listen
to
the
same
top,
so
how
do
I
will
remove
it,
and
I
will
do
the
same
here.
B
Yeah
basically
here
also
defining
to
consumers,
which
will
listen
to
this
queue
so
to
our
to
use
related
to
the
categories
and
related
to
the
two
products
and
yeah.
The
consumer
instance
is
the
same.
So
doesn't
change
here,
yep,
that's
it!
I
also
will
remove
this
one
and
what
I
will
do
now?
I
will
just
close
all
this
trash
key
I.
B
B
If
you
don't
want
to
have
mass
and
to
overload
your
memory
with
not
require
data,
because
this
queues
to
listen
for
those
topic
names
I
would
propose
to
remove
it
and
then,
when
you
will
start
stop
upgrade
what
magenta
will
do
button
to
reach
those
configuration
files
which
we
edit
it
and
it's
create
it
will
create.
Then
you
to
new
cues,
especially
especially
for
us.
B
B
D
B
We'll
take
bit
longer
because
of
the
cache
and
also
will
secret
categories,
and
if
and
now
we'll
check
my
table,
that's
our
request.
I
didn't
run
any
consumer
yet
so
that's
why
they
all
pending.
They
are
not
executed.
Okay,
and
we
have
here
the
products
like
here's.
A
point
product
here
come
in
the
categories
and
if
I
will
run
here,
the
categories.
B
Yeah
executed
only
the
category
queue
and
didn't
touch
any
product,
I
mean
yeah.
Here's
an
error
because
we
already
have
categories
with
those
names
and
it's
time
to
create
the
same
URL
key,
which
is
which
is
totally
fine,
but
just
one
I'm
going
to
show
that,
with
this
occasion,
exactly
this
queue
I
run
and
say
only
categories,
important
product
I'm,
not
touching.
B
In
this
way,
I
can
split
my
Ballack
to
the
different
consumers
and
different
queues
flows,
which
will
make
like
more
strict
understanding
what's
been
executed.
Yeah
can
be
quite
useful,
also
from
performance
point
no
point
of
view.
I
will,
let
say
not
recommend
to
run
20
consumers
or
a
product
creation,
because
Magento
may
have
a
deadlocks
on
the
tables,
but
I
would
definitely
suggest
to
run
separated
product
and
categories
because
they
and
let's
say,
has
no
or
almost
no
common
common
tables,
and
there
will
be
much
less
problems
if
you
run
multiple
yeah.
B
Our
QA
scheme
is
during
the
performance
testing
of
our
KPI,
like
last
two
weeks
as
we
playing
around
with
environment
and
the
first
results
we
get.
That
basically
looks
like
this.
I
mean
it's
not
really
explanatory,
because
the
self
generated
stuff
and
protect
make
it
fancy.
But
that's
basically
response
time
on
accepting
the
request
and
what
is
it
doing
to
be
false
and,
let's
say
a
syncope
I
know.
B
Synchro
knows
like
standard
TP
is
syncope
and
both
KPI
for
one
request,
then
for
two
requests
at
the
same
time,
at
the
same
time
and
for
three
and
then
to
300
requests
in
time
and
that's
a
response.
Time
of
them
and
the
red
line
is
usual
Magento
API.
So
basically,
what
is
doing
is
accepting
those
requests
and
like
sort
of
6
seconds
taking
if
you
send
in
really
data
at
the
same
time
like
the
slow,
the
slowest
one.
B
Yes
at
the
same
time,
it's
also
running
the
products
creation.
So
that's
it
not
only
acceptance,
it's
also
creating
but
yeah.
If
you'll
send
in
the
millions
of
them.
You
may
have
a
big
problem
or
it
will
take
too
long
if
you
will
send
them
only
one
one
by
one,
then
we
have
a
similar
CPI
which
worked
in
like
faster
I,
mean
and
always
like
twenty,
maybe
fifteen
percent
of
the
performance
improvement,
but
yeah
take
care
of
that.
B
A
Ok,
cool
awesome,
yeah,
so
thank
you
to
the
two
Alexes
for
showing
that
I
think
it
was
important
to
see
a
few
examples
of
how
we
can
get
working
with
with
bulk
API
in
the
in
your
projects.
So
hopefully
you
found
that
useful
and
please
please
reach
out
to
us.
If
you
have
the
topics
you
would
like
to
see
in
future,
hangouts
we're
currently
looking
for
the
next
two
to
be
around
and
dev
Docs,
and
what
the
good
stuff
is
going
on
there,
as
well
as
MFD
F
F,
a
testing
framework
England
another
couple.
A
So
hopefully
this
has
been
abused
to
you
as
I
said
before.
If
you're
an
Imagine
come
down
with
a
contribution,
they
come
say,
hi
we'll
have
a
few
of
our
team
members
around
through
the
whole
event
as
well,
so
come
say
hi
to
any
of
us
at
any
point.
If
you
have
any
feedback
or
anything
during
yeah
feel
free
to
reach
out
during
the
event,
and
of
course,
if
you
have
anything
that
you
really
want
to
know
or
you've
got
more
questions,
you
can
reach
out
to
us
through
our
Twitter
account.
A
If
you
are
in
the
slack
and
feel
free
to
reach
out
to
any
of
the
team
members
in
our
slack
and
yeah
or
by
email
and
that
is,
and
compact
adobe.com
I
think
the
magenta
one
still
works,
but
you
it'll
definitely
work
and
other
than
that.
I
would
like
to
say
see
you
next
time,
I
guess
thank
you
Alex
and
Alex
and
yeah.
Thanks
for
watching.