May 24, 2012

Post: Shard-Query EC2 images available

row in set (0.00 sec) With ICE, after compression there is only 2.5GB ofof the the AMI images. You should spin a number of instances that evenly divides into 20 for best results. There is a helpful utility (included in the

Post: Heikki Tuuri answers to Innodb questions, Part II

the only rule of thumb I seem to find is “INNODB should get around 70-80%” of the available RAM. I would guess that the numberin an ascending order of the PRIMARY KEY, then InnoDB should have placed the rows in contiguous blocks of

Post: Goal driven performance optimization

in user information etc. But the real thing is number of times which are stored for request. wall clock time – is therows in set (2.37 sec) As you can see in this case during certain hours the average type of