Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I don’t think innoDB could work because I need to truncate often very large tables (some GB) and i need every bit of disk space.
I have 3 tables that contain over 2 millions rows. I need to do a large number of queries for second (>50). I have only one user.
InnoDBtables area transactional and only useful where you may need to revert a commit in case something goes wrong specifically in a RDMBS environment. Based on the information you have provided which is not to none, if your only requirement is fast reads and writes I would say go withMyISAM. There are other engines too which are in-memory (definitely not a good idea with GB’s of data) and have various other properties, but without more details it’s hard to say if one of the others is a better fit.