|
From: Tatsuo I. <is...@po...> - 2012-11-15 04:47:58
|
>> PostgreSQL Enterprise Consortium is planning to do a benchmark against >> Postges-XC. If we would use standard pgbench workload(pgbench default, >> -N, -S), what is a recommended portioning plan for pgbench_accounts? >> > If you want to show up the scalability, I recommend that you use pgbench > with option -k for initialization and launching, which is an option that > has been added in the pgbench version of XC available in its source code. > This allows to to a benchmark test by using bid as a distribution key so > this minimizes the amount of 2PC done when write operations involve several > nodes in a transaction. > $ pgbench --help > Initialization options: > -k distribute by primary key branch id - bid > Benchmarking options: > -k query with default key and additional key branch id (bid) > > Depending on your cluster structure, I would also recommend you also to use > PREFERRED node with ALTER NODE (ALTER NODE nodename WITH (PREFERRED)) for > example with the Datanode that is on the same server as a Coordinator if > you use a structure of 1 Coordinator and 1 Datanode per server. This also > reduces the network load by having replicated table read being done on the > preferred node in priority. This is especially better if the node is local > of course. Thanks for suggestion. We did pgbench -k benchmark and got good result. Details will be published at PGECONS seminar on December 7th in Tokyo. https://www.pgecons.org/2012/12/07/1527/ Also I would like to do some read-only workload benchmark as well. Any suggestion to get good result? I'm not sure if plain pgbench -S gives good result. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp |