What if there is a problem with the data speed around 1E for a table in MySQL? Only if the where primary key id = XXX Query Other queries will not have.
Reply content:
What if there is a problem with the data speed around 1E for a table in MySQL? Only if the where primary key id = XXX Query Other queries will not have.
"E" is "billion" is not EB it? MySQL is generally recommended for single-table data up to 500w~1kw, mainly due to the index. If only the ID query, you should be able to deal with, this you can do a test to see how the throughput.
In other words, your needs are more suitable for simple key/value databases, no need to use MySQL.
In addition to the amount of data, how frequently is the frequency of access?
If that's what you're talking about. The most efficient way to access the primary key is to estimate the concurrency processing power in the worst case of a physical IO each time.
Since you said that only through the primary key query may not meet the actual requirements, if this is true, please estimate the concurrency, concurrency is very large, any efficient query DBMS will cause high IO throughput, can choose the document database MongoDB storage or query before adding memcache cache, Reduce database query pressure