On Fri, Dec 5, 2008 at 5:29 PM, Greg Smith <[EMAIL PROTECTED]> wrote:
> XFS has good performance, but I can't get over how many system failure
> corruption reports I hear about it. In any case, there's no reason this
> system shouldn't perform fine on ext3.
For simple testing you can take the fi
On Fri, 5 Dec 2008, Alan Hodgson wrote:
1) /sbin/blockdev --setra 2048 device (where device is the partition or
LVM volume)
Normally, when I see write speed dramatically faster than write, it does
mean that something about the read-ahead is set wrong. While I don't have
one to check, it loo
> >>> Mario Weilguni <[EMAIL PROTECTED]> wrote:
> > strange values. An individual drive is capable of delivering 91
> > MB/sec
>
> > sequential read performance, and we get values ~102MB/sec out of a
> > 8-drive RAID5, seems to be ridiculous slow.
What command are you using to test the reads?
S
On Tue, Dec 2, 2008 at 2:22 AM, Mario Weilguni <[EMAIL PROTECTED]> wrote:
> Has anyone benchmarked this controller (PCIe/4x, 512 MB BBC)? We try to use
> it with 8x SATA 1TB drives in RAID-5 mode under Linux, and measure strange
> values. An individual drive is capable of delivering 91 MB/sec seque
>>> Mario Weilguni <[EMAIL PROTECTED]> wrote:
> Has anyone benchmarked this controller (PCIe/4x, 512 MB BBC)? We try
to
> use it with 8x SATA 1TB drives in RAID-5 mode under Linux, and
measure
> strange values. An individual drive is capable of delivering 91
MB/sec
> sequential read performance
>>> "Omar Kilani" <[EMAIL PROTECTED]> wrote:
> During CS storm:
> count(*) from pg_locks - 1000 - 1400
What do you have for max_connections?
With the hardware and load you describe, I would guess you would limit
context switching and see best performance with a connection pool that
queues re
Laurenz Albe wrote:
> You have been ordered to use a partial index?
>
> > Apart from this I don't really understand why statement preparation
> > combined with parameters in functions prevent index invocation.
> > Especially since p_id_user is a parameter as well which doesn't
> > prevent the us
Rogatzki Rainer wrote:
> > > in a trigger-function (on update before):
> > >
> > > ...
> > > for c in
> > > select id_country, sum(cost) as sum_cost
> > > from costs
> > > where id_user = p_id_user
> > > and id_state = 1
> > > and date(request) between p_begin and p_until
>
am Fri, dem 05.12.2008, um 14:23:33 +0100 mailte Rogatzki Rainer folgendes:
> Hello Andreas,
>
> your hint did the trick - thank you very much!
glad to help you...
Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header)
GnuPG-ID: 0x3FFF606C, priva
> > Rogatzki wrote:
> > -- Example with bad performance since index isn't used
> > explain
> > select c.id_country, sum(c.cost) as sum_cost
> > from costs c, accounting_interval a
> > where c.id_user = 123
> > and c.id_state = 1
> > and a.id = 1
> > and date(c.request) between a.p_
am Fri, dem 05.12.2008, um 11:41:11 +0100 mailte Rogatzki Rainer folgendes:
> -- Example with bad performance since index isn't used
> explain
> select c.id_country, sum(c.cost) as sum_cost
> from costs c, accounting_interval a
> where c.id_user = 123
> and c.id_state = 1
> and a.id
> Rogatzki Rainer wrote:
> > I'm having problems with the following bad performing
select-statement
> > in a trigger-function (on update before):
> >
> > ...
> > for c in
> > select id_country, sum(cost) as sum_cost
> > from costs
> > where id_user = p_id_user
> > and id_state
Rogatzki Rainer wrote:
> I'm having problems with the following bad performing select-statement
> in a trigger-function (on update before):
>
> ...
> for c in
> select id_country, sum(cost) as sum_cost
> from costs
> where id_user = p_id_user
> and id_state = 1
> and date(r
13 matches
Mail list logo
