How to query a table ... or do I always have to process all records?

Okay, I’m listening, but I don’t see a clearly presented reason you don’t agree. Here’s why I believe my assertion is correct.

Scenario:

• A recycling company has 50 van drivers crisscrossing London picking up an average of ten loads each per day.
• They use the Tookan platform to indicate when they arrive at a job and when they finish collecting the recycled goods.
• Tookan fires a webhook for each of these two events for all fifty drivers; approximately 1,000 events.
• The receiving Airtable webhook needs to link three different tables to the order which reaches two different states - first when they start the job, and then when they complete the job. The linked relationships provide lookups into details concerning the load size, the company the driver works for, and other location data concerning postal codes and taxing authorities.
• To create this collection of links and modify them when the job is complete, three different lookups must occur to map the detail records into the order record.

I’m convinced there are many ways to address these requirements but a few things are clear:

1. Each of the three tables must be queried.
2. A lookup into each of the three tables must be performed.
3. A linked record to the order must be established in each table.

My data shows the following given four different approaches. If we extrapolate these values my cached hash seems to win once you pass about 50 updates.

If you have some different data or a better approach for evaluating this, let me know.