# Batched Orchestration

{% hint style="warning" %}
**We are suspending our support of Cypress test runner version 13+**

We will continue to support [prior versions](/getting-started/other-frameworks/cypress/integrating-with-cypress/alternative-cypress-binaries.md) of Cypress.

[Read more](https://currents.dev/posts/v13-blocking)
{% endhint %}

### Batched Orchestration

This package uses its own orchestration and reporting protocol that is independent of cypress native implementation. This approach provides several benefits, including more control, flexibility and the ability to implement new features that are not supported by the native cypress orchestration.

{% hint style="info" %}
Please note: the batched orchestration is not yet available for sorry-cypress users (only for currents.dev)
{% endhint %}

The new approach can present a slightly different performance compared to the previous integration. To enhance its performance, the new orchestration protocol allows multiple spec files to be batched together for greater efficiency. You configure the batching in `cypress.config.js` and use different values for different testing types:

```javascript
// currents.config.js
module.exports = {
  // ...
  e2e: {
    batchSize: 3, // orchestration batch size for e2e tests (Currents only)
  },
  component: {
    batchSize: 5, // orchestration batch size for component tests (Currents only)
  },
};

```

Based on our benchmarks, the performance is comparable to that of the native orchestration, however, it can vary depending on your specific configuration and setup. Adjusting the batching configuration can help to achieve optimal results for e2e or component tests.

#### Native Orchestration Diagram

{% @mermaid/diagram content="sequenceDiagram
loop while no specs left
Cypress Runner ->> Cloud Service: Get Next Spec File
Cloud Service -->> Cypress Runner: Spec File
activate Cypress Runner
Cypress Runner ->> Cypress Runner: executing Spec File
Cypress Runner ->> Cloud Service: Report Result for Spec File
deactivate Cypress Runner
end" %}

#### Batched Orchestration Diagram

{% @mermaid/diagram content="sequenceDiagram
loop while no specs are left
Cypress Runner ->> Cloud Service: Get Next Spec Files Batch
Cloud Service -->> Cypress Runner: SpecFileA, SpecFileB, SpecFileC
activate Cypress Runner
Cypress Runner ->> Cypress Runner: executing SpecFileA, SpecFileB, SpecFileC
Cypress Runner ->> Cloud Service: Report Result for SpecFileA, SpecFileB, SpecFileC
deactivate Cypress Runner
end
" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.currents.dev/resources/reporters/cypress-cloud/batched-orchestration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.