Am 15.05.2014 14:26, schrieb Antonio Fernández Pérez: > I have in my server database some tables that are too much big and produce > some slow query, even with correct indexes created. > > For my application, it's necessary to have all the data because we make an > authentication process with RADIUS users (AAA protocol) to determine if one > user can or not navigate in Internet (Depending on the time of all his > sessions). > > So, with 8GB of data in one table, what are your advices to follow? > Fragmentation and sharding discarted because we are working with disk > arrays, so not apply. Another option is to delete rows, but in this case, I > can't. For the other hand, maybe de only possible solution is increase the > resources (RAM)
rule of thumbs is innodb_buffer_pool = database-size or at least as much RAM that frequently accessed data stays always in the pool
signature.asc
Description: OpenPGP digital signature