Any idea why hypertable insert rates were slower? I though hypertables were supposed to _increase_ insert rates?
Indexes are per chunk. So if the query analyzer understands you only touch 2023 it can omit looking at any chunk that is from other years and keep those out of memory. Same with the indexes.
I know Timescale has a blog post from 2017 claiming a 20x higher insert rate but that's for inserting into a table with an index. The general wisdom for loading huge amounts of data seems to be that you should insert into a table with no indexes then build them later though. So with no index, inserting into a hypertable seems a bit slower.
Timescale blog post: https://medium.com/timescale/timescaledb-vs-6a696248104e