| To: | Rod Taylor <rbt@xxxxxx> |
|---|---|
| Subject: | Re: [PERFORM] PostgreSQL Reliability when fsync = false on Linux-XFS |
| From: | Hannu Krosing <hannu@xxxxx> |
| Date: | Thu, 04 Sep 2003 09:55:27 +0300 |
| Cc: | Federico Sevilla III <jijo@xxxxxxxxxxx>, PostgreSQL Performance Mailing List <pgsql-performance@xxxxxxxxxxxxxx>, Linux-XFS Mailing List <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <1062646595.84923.35.camel@jester> |
| References: | <20030904030404.GA32319@leathercollection.ph> <1062646595.84923.35.camel@jester> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Rod Taylor kirjutas N, 04.09.2003 kell 06:36: > Another alternative is > to buy a small 15krpm disk dedicated for WAL. In theory you can achieve > one commit per rotation. One commit per rotation would still be only 15000/60. = 250 tps, but fortunately you can get better results if you use multiple concurrent backends, then in the best case you can get one commit per backend per rotation. ----------------- Hannu |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Building 2.4.20-19 for RH 7.3, Joshua Baker-LePain |
|---|---|
| Next by Date: | PostgreSQL Reliability when fsync = false on Linux-XFS, Federico Sevilla III |
| Previous by Thread: | Re: PostgreSQL Reliability when fsync = false on Linux-XFS, Rod Taylor |
| Next by Thread: | Re: [PERFORM] PostgreSQL Reliability when fsync = false on Linux-XFS, scott.marlowe |
| Indexes: | [Date] [Thread] [Top] [All Lists] |