I am developing a system, and going deeper into the numbers, I understand that it can reach the point where there can be a table with 54,240,211,584 reports per year (approximately). WOW !!!!
So, I chop it down and down to 73,271,952 records / year (approximately).
I got the numbers by doing some excel on what would happen if:
a) no success = 87 users,
b) low moderate success = 4300 users,
c) high moderate success = 13199 users,
d) success = 55100 users
e) incredible success = nah
Taking into account that the table is used for SELECT, INSERT, UPDATE and JOIN statements and that these statements will be executed by any user registered in the system hourly / daily / weekly (historical data is not an option):
Question 1: this is the 2nd number suitable / convenient for the MySQL engine, so performance will have little impact.
Question 2: I installed the table as InnoDB, but considering the fact that I process all the instructions using JOINS and that I am ready to work with the 4 GB limitation problem, is InnoDB useful?
:
№ 1: /. 15 , VARCHAR.
№2: . 8 , TINYINT. INT. 4 15 , # 1.
№3: . 4 , TINYINT. INT. 3 , №2. , - ...
№3 . , 2- , , №3 № 2.
-, , .
, - :
i) 33,754,240,211,584: , .
ii) 3,375,424,021,158: , .
iii) 337,542,402,115: , . , - ", ..."
" "??? 1 000 000 3 . 33,754,240,211,584 10 , .
? , . , . , - . ,
.