> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/guides/ci-optimization.md).

# CI Optimization

A guide on optimizing Playwright tests in CI for better efficiency

Currents offers several ways to speed up and optimize your CI pipeline. Whether you’re just starting with basic test sharding or looking to squeeze every bit of efficiency from your infrastructure, the following strategies can help you reduce runtime, cut costs, and make test results more actionable.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Speed up CI by running Playwright Tests in Parallel</strong></td><td>Start with sharding and switch to Currents Orchestration for more efficient use of resource.<br><br><strong>Speed up CI by up to 50%</strong></td><td><a href="/guides/ci-optimization/playwright-parallelization.md">Playwright Parallelization</a></td></tr><tr><td><strong>Reduce CI costs with</strong><br><strong>Cloud Spot Instances</strong></td><td>Dynamically reroute tests from a to-be-terminated to a healthy instance.<br><br><strong>Save CI costs by up to 70%</strong></td><td><a href="/guides/ci-optimization/ci-tests-on-spot-instances.md">Cloud Spot Instances</a></td></tr><tr><td><strong>Enable Playwright Fully Parallel Mode</strong></td><td>Run tests from the same test file in parallel using all the available CPUs.</td><td><a href="/guides/ci-optimization/fully-parallel-mode.md">Fully Parallel Mode</a></td></tr><tr><td><strong>Explore Load Balancing Strategies</strong></td><td>Run frequently failing or flaky tests first with Currents Orchestration.</td><td><a href="/guides/ci-optimization/load-balancing.md">Load Balancing</a></td></tr><tr><td><strong>Re-run only failed tests</strong></td><td>Save CI computing time by re-running only tests that have failed.</td><td><a href="/guides/ci-optimization/re-run-only-failed-tests.md">Re-run Only Failed Tests</a></td></tr><tr><td><strong>Fail-fast</strong></td><td>Automatically cancel your test suite right after the first failure.</td><td><a href="/guides/ci-optimization/fail-fast-strategy.md">Failing Fast</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/guides/ci-optimization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.