Re: [PERFORM] Very poor read performance, query independent

2017-07-25 Thread Charles Nadeau
know more about Postgresql tuning. Charles On Mon, Jul 10, 2017 at 4:03 PM, Charles Nadeau <charles.nad...@gmail.com> wrote: > I’m running PostgreSQL 9.6.3 on Ubuntu 16.10 (kernel 4.4.0-85-generic). > Hardware is: > > *2x Intel Xeon E5550 > > *72GB RAM > > *Hardware RA

Re: [PERFORM] Very poor read performance, query independent

2017-07-20 Thread Charles Nadeau
15/07/17 11:09, Mark Kirkwood wrote: > >> Ah yes - that seems more sensible (but still slower than I would expect >> for 5 disks RAID 0). >> > > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to you

Re: [PERFORM] Very poor read performance, query independent

2017-07-19 Thread Charles Nadeau
k. Thanks! Charles On Tue, Jul 18, 2017 at 8:01 PM, Justin Pryzby <pry...@telsasoft.com> wrote: > On Tue, Jul 18, 2017 at 02:13:58PM -0300, Claudio Freire wrote: > > On Tue, Jul 18, 2017 at 1:01 PM, Claudio Freire <klaussfre...@gmail.com> > wrote: > > > On T

Re: [PERFORM] Very poor read performance, query independent

2017-07-18 Thread Charles Nadeau
PM, Claudio Freire <klaussfre...@gmail.com> wrote: > On Fri, Jul 14, 2017 at 12:34 PM, Charles Nadeau > <charles.nad...@gmail.com> wrote: > > Workers Planned: 12 > > Workers Launched: 12 > >

Re: [PERFORM] Very poor read performance, query independent

2017-07-17 Thread Charles Nadeau
ort) "flows_srcport_dstport_idx" btree (srcport, dstport) Thanks! Charles On Fri, Jul 14, 2017 at 10:18 PM, Igor Neyman <iney...@perceptron.com> wrote: > > > > > *From:* pgsql-performance-ow...@postgresql.org [mailto:pgsql-performance- > ow...@postgresql.

Re: [PERFORM] Very poor read performance, query independent

2017-07-16 Thread Charles Nadeau
Scott, The temp tablespace is on a disk of his own. Thanks! Charles On Sat, Jul 15, 2017 at 7:58 PM, Scott Marlowe <scott.marl...@gmail.com> wrote: > On Sat, Jul 15, 2017 at 11:53 AM, Charles Nadeau > <charles.nad...@gmail.com> wrote: > > Mark, > > > >

Re: [PERFORM] Very poor read performance, query independent

2017-07-16 Thread Charles Nadeau
! Charles On Fri, Jul 14, 2017 at 9:13 PM, Igor Neyman <iney...@perceptron.com> wrote: > *From:* Charles Nadeau [mailto:charles.nad...@gmail.com] > *Sent:* Friday, July 14, 2017 11:35 AM > *To:* Igor Neyman <iney...@perceptron.com> > *Cc:* Jeff Janes <jeff.ja...@gma

Re: [PERFORM] Very poor read performance, query independent

2017-07-15 Thread Charles Nadeau
RAID stripe size - for DW work it makes sense > for it to be reasonably big (256K to 1M), which again will help speed is > sequential scans. > > Cheers > > Mark > > P.s I used to work for Greenplum, so this type of problem came up a lot > :-) . The best cards were the LSI and

Re: [PERFORM] Very poor read performance, query independent

2017-07-15 Thread Charles Nadeau
k > > On 15/07/17 11:09, Mark Kirkwood wrote: > >> Ah yes - that seems more sensible (but still slower than I would expect >> for 5 disks RAID 0). >> > > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make chan

Re: [PERFORM] Very poor read performance, query independent

2017-07-14 Thread Charles Nadeau
wscompact.dstaddr FROM flowscompact LEFT JOIN mynetworks ON mynetworks.ipaddr >> flowscompact.dstaddr::ip4r WHERE mynetworks.ipaddr IS NULL; Thanks! Charles On Wed, Jul 12, 2017 at 6:39 PM, Igor Neyman <iney...@perceptron.com> wrote: > > > > > *From:* pgsql-perfor

Re: [PERFORM] Very poor read performance, query independent

2017-07-14 Thread Charles Nadeau
svctm %util > sda 0.00 0.00 926.000.00 114.89 0.00 254.10 >1.902.032.030.00 1.08 100.00 > > > So might be useful for us to see something like that from your system - > note you need to check you really have flushed the cache, and that no

Re: [PERFORM] Very poor read performance, query independent

2017-07-12 Thread Charles Nadeau
oot cause, at the least I would set up > hugepages ( https://www.postgresql.org/docs/9.6/static/kernel- > resources.html#LINUX-HUGE-PAGES ), and bump effective_io_concurrency up > quite a bit as well (256 ?). > > > On Mon, Jul 10, 2017 at 10:03 AM, Charles Nadeau <charles.nad...

Re: [PERFORM] Very poor read performance, query independent

2017-07-12 Thread Charles Nadeau
hit=10 Planning time: 6.689 ms Execution time: 2764860.853 ms (58 rows) Regarding "Also using dstat I can see that iowait time is at about 25%", I don't think the server was doing anything else. If it is important, I can repeat the benchmarks. Thanks! Charles On Wed, Jul 12, 2017 at 2:39 AM,

Re: [PERFORM] Very poor read performance, query independent

2017-07-12 Thread Charles Nadeau
] deadline cfq Thanks! Charles On Wed, Jul 12, 2017 at 1:42 AM, Joshua D. Drake <j...@commandprompt.com> wrote: > On 07/11/2017 04:15 PM, Merlin Moncure wrote: > >> On Mon, Jul 10, 2017 at 9:03 AM, Charles Nadeau >> <charles.nad...@gmail.com> wrote: >> >>>

Re: [PERFORM] Very poor read performance, query independent

2017-07-12 Thread Charles Nadeau
? Thanks! Charles On Tue, Jul 11, 2017 at 5:16 PM, Igor Neyman <iney...@perceptron.com> wrote: > > > *From:* pgsql-performance-ow...@postgresql.org [mailto:pgsql-performance- > ow...@postgresql.org] *On Behalf Of *Igor Neyman > *Sent:* Tuesday, July 11, 2017 10:34 AM &

Re: [PERFORM] Very poor read performance, query independent

2017-07-11 Thread Charles Nadeau
Igor, The sum of effective_cache_size and shared_buffer will be higher than the physical memory I have. Is it OK? Thanks! Charles On Tue, Jul 11, 2017 at 4:34 PM, Igor Neyman <iney...@perceptron.com> wrote: > > > *From:* Charles Nadeau [mailto:charles.nad...@gmail.com] > *Se

Re: [PERFORM] Very poor read performance, query independent

2017-07-11 Thread Charles Nadeau
@postgresql.org [mailto:pgsql-performance- > ow...@postgresql.org] *On Behalf Of *Charles Nadeau > *Sent:* Monday, July 10, 2017 11:48 AM > *To:* Andreas Kretschmer <andr...@a-kretschmer.de> > *Cc:* pgsql-performance@postgresql.org > *Subject:* Re: [PERFORM] Very poor

Re: [PERFORM] Very poor read performance, query independent

2017-07-11 Thread Charles Nadeau
97594904 Could you suggest another way to benchmark random reads? Thanks for your help! Charles On Mon, Jul 10, 2017 at 9:24 PM, Jeff Janes <jeff.ja...@gmail.com> wrote: > On Mon, Jul 10, 2017 at 7:03 AM, Charles Nadeau <charles.nad...@gmail.com> > wrote: > >> >>

Re: [PERFORM] Very poor read performance, query independent

2017-07-11 Thread Charles Nadeau
wrote: > > > *From:* pgsql-performance-ow...@postgresql.org [mailto:pgsql-performance- > ow...@postgresql.org] *On Behalf Of *Charles Nadeau > *Sent:* Monday, July 10, 2017 11:48 AM > *To:* Andreas Kretschmer <andr...@a-kretschmer.de> > *Cc:* pgsql-performance@postgresql.org >

Re: [PERFORM] Very poor read performance, query independent

2017-07-11 Thread Charles Nadeau
> > > On Mon, Jul 10, 2017 at 10:03 AM, Charles Nadeau <charles.nad...@gmail.com > > wrote: > >> I’m running PostgreSQL 9.6.3 on Ubuntu 16.10 (kernel 4.4.0-85-generic). >> Hardware is: >> >> *2x Intel Xeon E5550 >> >> *72GB RAM >> >&

Re: [PERFORM] Very poor read performance, query independent

2017-07-10 Thread Charles Nadeau
wrote: > > > Am 10.07.2017 um 16:03 schrieb Charles Nadeau: > >> random_page_cost | 22 >> > > > why such a high value for random_page_cost? > > Regards, Andreas > > -- > 2ndQuadrant - The PostgreSQL Support Company. > www.2ndQuadrant.com >

[PERFORM] Very poor read performance, query independent

2017-07-10 Thread Charles Nadeau
esn’t seem to have any issues, I am really puzzled. Thanks! Charles -- Charles Nadeau Ph.D.