Database speed optimization: few tables with many rows, or many tables with few rows?

Question

I have a big doubt.

Let\'s take as example a database for a whatever company\'s orders.

Let\'s say that this company make around 2000 orders per month, so, a

Answer 1

I would not split tables by year.

Instead I would archive data to a reporting database every year, and use that when needed.

Alternatively you could partition the data, amongst drives, thus maintaining performance, although i'm unsure if this is possible in postgresql.