On Thu, Nov 6, 2008 at 8:07 AM, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 6, 2008 at 8:47 AM, David Rees <[EMAIL PROTECTED]> wrote:
>>
>> In the case of the machines without a BBU on them, they are configured
>> to be in WriteBack, but are actually running in WriteThrough.
>
> I'm pret
On Thu, Nov 6, 2008 at 8:47 AM, David Rees <[EMAIL PROTECTED]> wrote:
>
> In the case of the machines without a BBU on them, they are configured
> to be in WriteBack, but are actually running in WriteThrough.
I'm pretty sure the LSIs will refuse to actually run in writeback without a BBU.
--
Sen
On Thu, Nov 6, 2008 at 2:21 AM, Peter Schuller
<[EMAIL PROTECTED]> wrote:
>> I also found that my write cache was set to WriteThrough instead of
>> WriteBack, defeating the purpose of having a BBU and that my secondary
>> server apparently doesn't have a BBU on it. :-(
>
> Note also that several RA
> I also found that my write cache was set to WriteThrough instead of
> WriteBack, defeating the purpose of having a BBU and that my secondary
> server apparently doesn't have a BBU on it. :-(
Note also that several RAID controllers will periodically drop the
write-back mode during battery capacit
On Fri, Oct 31, 2008 at 4:14 PM, David Rees <[EMAIL PROTECTED]> wrote:
> Well, I'm pretty sure the delays are not checkpoint related. None of
> the slow commits line up at all with the end of checkpoints.
>
> The period of high delays occur during the same period of time each
> week, but it's not d
(Resending this, the first one got bounced by mail.postgresql.org)
On Wed, Oct 29, 2008 at 3:30 PM, David Rees <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 29, 2008 at 6:26 AM, Greg Smith <[EMAIL PROTECTED]> wrote:
>> What you should do first is confirm
>> whether or not the slow commits line up with
On Wed, Oct 29, 2008 at 6:26 AM, Greg Smith <[EMAIL PROTECTED]> wrote:
> The CentOS 4.7 kernel will happily buffer about 1.6GB of writes with that
> much RAM, and the whole thing can get slammed onto disk during the final
> fsync portion of the checkpoint. What you should do first is confirm
> whe
On Mon, 27 Oct 2008, David Rees wrote:
Software: CentOS 4.7, PostgreSQL 8.3.4, Slony-I 1.2.15 (the database
in question is replicated using slony)
Hardware: 2x Xeon 5130, 4GB RAM, 6-disk RAID10 15k RPM, BBU on the controller
The CentOS 4.7 kernel will happily buffer about 1.6GB of writes with
On Mon, Oct 27, 2008 at 05:23:37PM -0700, David Rees wrote:
> However, occasionally, processing time will jump up significantly -
> the average processing time is around 20ms with the maximum processing
> time taking 2-4 seconds for a small percentage of transactions. Ouch!
>
> Turning on stateme
On Mon, Oct 27, 2008 at 8:23 PM, David Rees <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've got an OLTP application which occasionally suffers from slow
> commit time. The process in question does something like this:
>
> 1. Do work
> 2. begin transaction
> 3. insert record
> 4. commit transaction
> 5. D
Hi,
I've got an OLTP application which occasionally suffers from slow
commit time. The process in question does something like this:
1. Do work
2. begin transaction
3. insert record
4. commit transaction
5. Do more work
6. begin transaction
7. update record
8. commit transaction
9. Do more work
11 matches
Mail list logo
