On 8/13/2026 7:21 AM, Robin Jarry wrote: > The REST API is slow. This is not news to anyone running a public > instance. The patchwork.ozlabs.org and patches.dpdk.org deployments have > both experienced outages when too many users or CI systems hit the API > concurrently. The codebase itself acknowledges this: multiple fields in > the API serializers are marked "too slow to calculate", patch tags are > disabled entirely because they are not performant, and offset-based > pagination becomes prohibitively expensive on large projects. Several > past releases have listed performance fixes as their headline feature, > yet the issues keep coming back because they are rooted in the framework > layer, not in the application logic.
I can't really attest to anything else but I can definitely confirm experience working the slow REST API and frustration that some basic concepts don't work due to these limitations. > > The REST API versions 1.0 through 1.4 are compatible with the existing > Django-based implementation. Existing clients (git-pw, snowpatch, or > custom scripts) should work without modification. The legacy XML-RPC API > has been removed entirely. > I imagine 4.x would be able to extend the REST API in the future to fix or improve some of the limitations that weren't fixable before? _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
