API Listing Rows - does size matter?

Technical Help
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

1.35

If you are self-hosting, which installation method do you use to run Baserow?

Debian Docker 1.35

What are the exact steps to reproduce this issue?

No issues, I’m just wondering if setting the ?size= parameter helps in performance? Will the API do an “early return”? Say if I set size=1, will the API stop searching for rows after it finds a match?

I’m using List Rows to “get” a single row, because of the {link_row_field}__join feature. But it’s understandably less performant than a simple GET row ID. Any tips on this would be much appreciated :slight_smile:

2

Hey @qcasey

size limits the number of rows returned, but it does not make the API “early return.”

For the List Rows endpoint, a total count is still computed, and all filters/joins are applied before returning the page.

You can pass adhoc filter like filter__id__equal=<row_id> in query parameter and that should limit results

Another optimizations to think about would be to use include parameter if you don’t need all fields, and avoid order_by