# CI Optimization

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="ci-optimization/playwright-parallelization">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="ci-optimization/ci-tests-on-spot-instances">ci-tests-on-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="ci-optimization/fully-parallel-mode">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="ci-optimization/load-balancing">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="ci-optimization/re-run-only-failed-tests">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="ci-optimization/fail-fast-strategy">fail-fast-strategy</a></td></tr></tbody></table>


---

# 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/guides/ci-optimization.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.