Re: How to get acceptable/repeatable performance on huge table

[Peter Stridsberg]

* How could "A secondary INDEX(aid, userUid) (or even simply INDEX(aid), which happens to be identical in InnoDB)):" be identical?


* Is it just to add an index on the Slave Db Table? It won't mess up the replication in any way?


SHOW VARIABLES LIKE 'query_cache_size';
+------------------+----------+
| Variable_name | Value |
+------------------+----------+
| query_cache_size | 33554432 |
+------------------+----------+
1 row in set (0.00 sec)

mysql> SHOW VARIABLES LIKE 'query_cache_type';
+------------------+--------+
| Variable_name | Value |
+------------------+--------+
| query_cache_type | DEMAND |
+------------------+--------+

* I suppose DEMAND strategy will work with no problems as long as we only cache certain key results?


RAM memory:
$ free
total used free shared buffers cached
Mem: 65995448 55999876 9995572 0 520592 3724636
-/+ buffers/cache: 51754648 14240800
Swap: 2031608 225048 1806560


innodb_buffer_pool_size = 48103424000