I am encountering performance problems with my database during peak hours at 140 qps average (max: 1000+ qps).
It is a dynamic service using a simple Innodb table, many concurrent read & writes, 3 million rows and growing.
It stores “posts” of about 90,000 accounts. My question would be, is it a good choice to split the posts into separate tables? E.g. a table for each account instead of one giant table.
Initially it was CPU bound and not I/O, but now I am no longer sure what problem it is.
I only wish to know whether it would be wise to split the tables at this point as I still have other optimizations going around at the moment. Many thanks.