| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 7 months |
| seen | Feb 10 at 5:35 | |
| stats | profile views | 14 |
|
Sep 30 |
awarded | Scholar |
|
Sep 30 |
comment |
Choosing MyISAM over InnoDB for these project requirements; and long term options Hmmm... Then I guess MyISAM is bad for my application after all; and since I've sorted out the InnoDB performance issue, I will be using it. Thanks! |
|
Sep 30 |
comment |
Choosing MyISAM over InnoDB for these project requirements; and long term options Query run time of InnoDB was a PITA, but I've sorted it out after setting an appropriate buffer pool size. So, I've chosen InnoDB for the long run. Thanks for all the information! |
|
Sep 28 |
awarded | Supporter |
|
Sep 27 |
comment |
Choosing MyISAM over InnoDB for these project requirements; and long term options "MyIsam tends to get corrupted at least once a month...high traffic website", uh, that's scary! Does "traffic" here mean only the majority reads for my site, or does it also include my comparitively low 2000 writes? |
|
Sep 26 |
revised |
Choosing MyISAM over InnoDB for these project requirements; and long term options added 359 characters in body |
|
Sep 26 |
comment |
Choosing MyISAM over InnoDB for these project requirements; and long term options @DTest - I ran the tests on v5.1.41, but for production I still haven't decided on the version or bought the server. |
|
Sep 26 |
awarded | Editor |
|
Sep 26 |
revised |
Choosing MyISAM over InnoDB for these project requirements; and long term options added 179 characters in body |
|
Sep 26 |
awarded | Student |
|
Sep 26 |
asked | Choosing MyISAM over InnoDB for these project requirements; and long term options |