| From: | "MauMau" <maumau307(at)gmail(dot)com> | 
|---|---|
| To: | <pgsql-performance(at)postgresql(dot)org> | 
| Subject: | Could synchronous streaming replication really degrade the performance of the primary? | 
| Date: | 2012-05-09 13:06:17 | 
| Message-ID: | 61B94EF1D7774715BC565DD84C731BDD@maumau | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-performance | 
Hello,
I've heard from some people that synchronous streaming replication has 
severe performance impact on the primary. They said that the transaction 
throughput of TPC-C like benchmark (perhaps DBT-2) decreased by 50%. I'm 
sorry I haven't asked them about their testing environment, because they 
just gave me their experience. They think that this result is much worse 
than some commercial database.
I'm surprised. I know that the amount of transaction logs of PostgreSQL is 
larger than other databases because it it logs the entire row for each 
update operation instead of just changed columns, and because of full page 
writes. But I can't (and don't want to) believe that those have such big 
negative impact.
Does anyone have any experience of benchmarking synchronous streaming 
replication under TPC-C or similar write-heavy workload? Could anybody give 
me any performance evaluation result if you don't mind?
Regards
MauMau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clemens Eisserer | 2012-05-09 13:27:39 | Re: Any disadvantages of using =ANY(ARRAY()) instead of IN? | 
| Previous Message | Merlin Moncure | 2012-05-09 12:53:01 | Re: scale up (postgresql vs mssql) |