This is running on a single AWS c5.metal instance. It has 196GB RAM, but we are using only 40GB at peak. The instance provides two 24-core CPUs, but we are only using one of them on 23-threads. So far, it's handling the flow of connections and requests from HN fine. We over provisioned just in case as we were not sure what to expect :-)

Storage is an AWS EBS volume.

Thanks for replying. What is the size of the data for these 1.6B rides? I'm assuming the data is on disk (SSD?) and not in-memory. Or, is Quest an in-memory DB?

The trips table takes 313GB. QuestDB is not an in-memory DB. The data sits on SSD EBS volumes.