100W I can't remember exactly but 1000W if you query it directly the efficiency is definitely a problem.

But if you write the SELECT statement in the stored procedure, the efficiency of the reduction is very small!

So all the operations on the database are encapsulated in stored procedures as much as possible.

We're working on something right now, and yesterday we measured 200 million rows of data, and it's fine--efficiency degradation was kept to an acceptable level.

Of course, I'm not going to get into good indexing, cache configuration, tuning, and so on.

Splitting tables, splitting libraries, load balancing, etc. are also solutions

That scenario you described above is possible.