--- title: Pushing testing laboratory performance limits by... description: Collabora's testing lab, running over 150 devices across ~30 device types and serving multiple CI systems (KernelCI, MesaCI, Apertis QA), explores how to... canonical: https://daily.dev/posts/pushing-testing-laboratory-performance-limits-by-benchmarking-lava-e5fcggdwf twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Pushing testing laboratory performance limits by benchmarking LAVA | daily.dev og:description: Collabora's testing lab, running over 150 devices across ~30 device types and serving multiple CI systems (KernelCI, MesaCI, Apertis QA), explores how to... og:url: https://daily.dev/posts/pushing-testing-laboratory-performance-limits-by-benchmarking-lava-e5fcggdwf og:image: https://api.daily.dev/og/posts/E5fCGGDWF.png og:image:alt: Pushing testing laboratory performance limits by benchmarking LAVA og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Pushing testing laboratory performance limits by benchmarking LAVA **[Collabora Blog](https://daily.dev/sources/collabora)** · 4 min read · 0 upvotes · 0 comments ## Summary Collabora's testing lab, running over 150 devices across ~30 device types and serving multiple CI systems (KernelCI, MesaCI, Apertis QA), explores how to benchmark and scale LAVA — the underlying test automation software. The post describes an initial benchmarking setup using docker-compose, a production database dump, Apache Benchmark, and pgAdmin, which helped identify and fix performance issues like branching logic inefficiencies and missing lazy pagination in the LAVA REST API. The challenge of guarding future patches against performance regressions is introduced, along with the distinction between downstream and upstream CI pipelines. The post is Part 1 of a series, with deeper topics promised in subsequent parts. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What performance issues were found and fixed in LAVA through benchmarking? Benchmarking a LAVA instance with a production database dump and Apache Benchmark revealed two concrete issues: suboptimal branching logic (fixed via an optimization patch) and missing lazy pagination in the LAVA REST API (introduced via a merge request). The setup used docker-compose, pgAdmin for PostgreSQL analysis, and mocked traffic to isolate server-side bottlenecks. _Teams running LAVA labs at scale track patches like these on daily.dev before they hit production._ ## Similar posts on daily.dev - [Shift Left Performance Testing in CI/CD: A Practical LoadRunner Framework](https://daily.dev/posts/shift-left-performance-testing-in-ci-cd-a-practical-loadrunner-framework-3vwynfmi9) · DevOps.com · 0 upvotes · 0 comments - [Elevating AI-assisted Android development and improving LLMs with Android Bench](https://daily.dev/posts/elevating-ai-assisted-android-development-and-improving-llms-with-android-bench-vcrh8h3bs) · Android Developers Blog · 0 upvotes · 0 comments - [Automating Web Performance Testing in CI](https://daily.dev/posts/automating-web-performance-testing-in-ci-6eh7jawda) · Halodoc · 2 upvotes · 0 comments - [I said your ELT benchmark was probably lying. Then mine lied to me — three times.](https://daily.dev/posts/i-said-your-elt-benchmark-was-probably-lying-then-mine-lied-to-me-three-times--ikymjzrrd) · Medium · 0 upvotes · 0 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#cicd](https://daily.dev/tags/cicd), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/pushing-testing-laboratory-performance-limits-by-benchmarking-lava-e5fcggdwf) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Pushing testing laboratory performance limits by benchmarking LAVA","url":"https://daily.dev/posts/pushing-testing-laboratory-performance-limits-by-benchmarking-lava-e5fcggdwf","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/pushing-testing-laboratory-performance-limits-by-benchmarking-lava-e5fcggdwf"},"datePublished":"2026-08-11T08:56:24.688Z","dateModified":"2026-08-11T09:28:26.115Z","description":"Collabora's testing lab, running over 150 devices across ~30 device types and serving multiple CI systems (KernelCI, MesaCI, Apertis QA), explores how to...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5b40e4ffe3b801df9ab3ab1c8829fc5f?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5b40e4ffe3b801df9ab3ab1c8829fc5f?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collabora Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collabora Blog","logo":"https://media.daily.dev/image/upload/s--ZGZ0FjqS--/f_auto,q_auto/v1786438306/logos/collabora?_a=BAMAMicg0","url":"https://daily.dev/sources/collabora"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/pushing-testing-laboratory-performance-limits-by-benchmarking-lava-e5fcggdwf","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,cicd,postgresql","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collabora Blog","item":"https://daily.dev/sources/collabora"},{"@type":"ListItem","position":3,"name":"Pushing testing laboratory performance limits by benchmarking LAVA"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/pushing-testing-laboratory-performance-limits-by-benchmarking-lava-e5fcggdwf#faq","mainEntity":[{"@type":"Question","name":"What performance issues were found and fixed in LAVA through benchmarking?","acceptedAnswer":{"@type":"Answer","text":"Benchmarking a LAVA instance with a production database dump and Apache Benchmark revealed two concrete issues: suboptimal branching logic (fixed via an optimization patch) and missing lazy pagination in the LAVA REST API (introduced via a merge request). The setup used docker-compose, pgAdmin for PostgreSQL analysis, and mocked traffic to isolate server-side bottlenecks. Teams running LAVA labs at scale track patches like these on daily.dev before they hit production."}}]} ```