tag:blogger.com,1999:blog-9149523927864751087.post2921037308290261950..comments2024-03-26T09:43:01.052-07:00Comments on Small Datum: Capacity planning and QPSMark Callaghanhttp://www.blogger.com/profile/09590445221922043181noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-9149523927864751087.post-12878182279154570942015-04-11T01:40:23.416-07:002015-04-11T01:40:23.416-07:00Not only that, a common mistake I see is: If your ...Not only that, a common mistake I see is: If your cluster has a maximum QPS per node, and you require availability of, let's say, supporting z node failures, then you need X/Y + z, otherwise your cluster will fail in cascade. Adding z extra nodes adds latency, etc. (aside from everything else you mention- DB thoughput is not everything).<br /><br />Now that InnoDB seems to completely replacing memory and MyISAM, and there are more "complex" (please note the quotes) tablespace management I would like to see some way to pinning InnoDB tables/indexes/partitions into memory without relaying on mounting memory.Jaime Crespohttp://dbahire.comnoreply@blogger.com