---
# System prepended metadata

title: '[Decathlon] Test performance central server'

---

# [Decathlon] Test performance central server 

## Questions

* How much quantity of elements are edited during synchronization iteration?
* We need a complete list of third-party integrations

## Product Side

### Used tool

* Jmeter

### Definition

#### Main goal

Test capicity of central server to handle all synchronization requests from local servers competitively

#### Goals

* Average time of a single synchronization iteration
* Define number limit for competitive synchronizations

#### Key numbers

* 3k+ local servers
* 64 distincts synchronization routes

#### Key information

* Each route could be paginated and result in multiple calls

#### Routes called during sync 

```
/api/synchronization/operations/attributes/attributes
/api/synchronization/operations/attributes_options/attribute/options
/api/synchronization/operations/attributes_types/attribute/types
/api/synchronization/operations/banks/accounts
/api/synchronization/operations/barcode/codes
/api/synchronization/operations/barcode/types
/api/synchronization/operations/capacity_templates
/api/synchronization/operations/capacity_template_exceptions
/api/synchronization/operations/cash/divisions
/api/synchronization/operations/cash_management_reasons
/api/synchronization/operations/categories
/api/synchronization/operations/category_entity_configurations
/api/synchronization/operations/category_externs
/api/synchronization/operations/catering/companies
/api/synchronization/operations/catering/payment_modes
/api/synchronization/operations/catering/periods
/api/synchronization/operations/catering/pricing_rules
/api/synchronization/operations/catering/tariff_components
/api/synchronization/operations/channels
/api/synchronization/operations/cohorts
/api/synchronization/operations/customers
/api/synchronization/operations/customer_divisions
/api/synchronization/operations/customer_refund_reasons
/api/synchronization/operations/customer_return_reasons
/api/synchronization/operations/destinations
/api/synchronization/operations/devices
/api/synchronization/operations/discounts
/api/synchronization/operations/eav/resources
/api/synchronization/operations/entities
/api/synchronization/operations/kvs/categories
/api/synchronization/operations/kvs/configs
/api/synchronization/operations/locales
/api/synchronization/operations/origins
/api/synchronization/operations/payments/configs
/api/synchronization/operations/payments/methods
/api/synchronization/operations/pos/configs
/api/synchronization/operations/pos/config_entities
/api/synchronization/operations/printers
/api/synchronization/operations/privacy/policies
/api/synchronization/operations/products/associations
/api/synchronization/operations/product/categories
/api/synchronization/operations/product/comments
/api/synchronization/operations/products
/api/synchronization/operations/product_entity_configurations
/api/synchronization/operations/products/groups
/api/synchronization/operations/product_messages
/api/synchronization/operations/products/prices
/api/synchronization/operations/product_suggestions
/api/synchronization/operations/products/ugc/product/ugcs
/api/synchronization/operations/resources
/api/synchronization/operations/resources/groups
/api/synchronization/operations/shift_reports/configs
/api/synchronization/operations/stock_types
/api/synchronization/operations/taxes
/api/synchronization/operations/types
/api/synchronization/operations/users
/api/synchronization/operations/users
/api/synchronization/operations/users/groups
/api/synchronization/operations/actions
/api/synchronization/operations/templates
/api/synchronization/operations/pim/categories/config_entities
/api/synchronization/operations/pim/discounts/config_entities
/api/synchronization/operations/divisions
/api/synchronization/operations/tags
```

## Project side

### Key information

* Synchronisation is incremental and manage by a file system


### Third party integrations

* POS log events ?