Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update order-management-system-multi-thread.md #2235

Merged
merged 3 commits into from
Mar 7, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,9 @@ console oms:check-timeout -p 1,2,3 -l 10000
```
{% info_block warningBox %}

If you have a large database, for performance reasons, it is not recommended to specify several comma-separated processor identifiers.
Processor identifiers distribution across the tasks should consider even distribution of the simulateneously processed orders.

To have the `-p` option applied, you need to use store the name by the `-s` option or limit by `-l`.
Option `-p` works only with a store name passed via option `--store-name` (or a short `-s`) or a limit via option `--limit` (or a short `-l`).

{% endinfo_block %}

Expand Down Expand Up @@ -116,4 +116,5 @@ $jobs[] = [
Regarding performance, there are a few things to keep in mind when running the OMS commands:

* The limit options: commands `oms:check-timeout` and `oms:check-condition` have an option that allows specifying the maximum number of order items to be handled during a single command run. It's recommended to provide this option for speeding up the database-related activities.

* You can specify more than one processor identifier for a single command run. But for large databases, this is generally not recommended. Specifying more than one process identifier affects the SQL query running under the hood and might disable a table index needed for this query to be executed in the most performant way.
Loading