Reputation: 1226
i'm designing a user log table that will log major user actions (login, logout, etc) - as you can imagine, this table will be hit for write very often, while read will be minimal.
I generally just go with innoDB for all my tables, but I'm wondering if this is the best way to go with a table that will be used for logs ?
Any recommendations for table type and other design issues ? thanks in advance.
Upvotes: 3
Views: 2735
Reputation: 1534
I think you must use Archive Storage Engine because logs are usually really huge and you will never read them. Archive Storage Engine also tuned for massive insertions.
Upvotes: 2
Reputation: 4341
MyISAM is faster, but does not support the use of transactions like InnoDB does. But, i think you don't need transactions for a log table, so MyISAM would be adequate.
Upvotes: 1