I'm also confused. 2. Agreed. 150 ms is extraordinarily slow for a point lookup from a single table. A simple lookup should take around 1 ms since it'll be cac

I'm also confused. 2. Agreed. 150 ms is extraordinarily slow for a point lookup from a single table. A simple lookup should take around 1 ms since it'll be cached in memory. 3. Also agreed. The actual database time looks to be the first flame. Hovering over it shows PG::Connection::exec which accounts for 2.5% of the time. I was curious about date parsing and dug up the source [1]. Seems like you could gain a ton of speed back by using a postgres specific timestamp parsing routine. In Go, it's 40 lines [2] [1] https://github.com/ruby/date/blob/d21c69450a57a1931ab61903854b31c0e5c9ec21/ext/date/date_parse.c#L2137 https://github.com/ruby/date/blob/d21c69450a57a1931ab6190385... [2]: https://github.com/jackc/pgx/blob/a968ce3437eefc4168b39bbc4b1ea685f4c8ae66/pgtype/timestamptz.go#L275 https://github.com/jackc/pgx/blob/a968ce3437eefc4168b39bbc4b...