Re: Query slow for new participants

2019-02-27 Thread supp...@mekong.be
Hello All, Thank you very much for your help. You have really helped me out! The query is now as fast as the others. The indexes ix_companyarticledb_article and ix_companyarticledb_company are removed. The parameter for default_statistics_target was set to 1000 ANALYZE was performed on the

Re: Query slow for new participants

2019-02-26 Thread Laurenz Albe
supp...@mekong.be wrote: > EXPLAIN (ANALYZE, BUFFERS), not just EXPLAIN > "Index Scan using ix_companyarticledb_company on companyarticledb > (cost=0.57..2.80 rows=1 width=193) (actual time=1011.335..1011.454 rows=1 > loops=1)" > " Index Cond: (companyid = 77)" > " Filter: (articleid = 7869071

Re: Query slow for new participants

2019-02-26 Thread Michael Lewis
> Indexes: > "pk_pricedb" PRIMARY KEY, btree (companyid, articleid) > "EnabledIndex" btree (enabled) > "ix_companyarticledb_article" btree (articleid) > "ix_companyarticledb_company" btree (companyid) > I'd say drop ix_companyarticledb_company since pk_pricedb can be used instead e

Re: Query slow for new participants

2019-02-26 Thread supp...@mekong.be
Hello, Things to Try Before You Post -> I went through these steps and they did not bring any difference. Information You Need To Include Postgres version "PostgreSQL 10.6 on x86_64-pc-linux-gnu, compiled by gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516, 64-bit" Full Table and Index Schema The di

Re: Query slow for new participants

2019-02-25 Thread MichaelDBA
Regarding shared_buffers, please install the pg_buffercache extension and run the recommended queries with that extension during high load times to really get an idea about the right value for shared_buffers. Let's take the guess work out of it. Regards, Michael Vitale Justin Pryzby

Re: Query slow for new participants

2019-02-25 Thread Justin Pryzby
On Tue, Feb 26, 2019 at 12:22:39AM +0100, supp...@mekong.be wrote: > Hardware > Standard DS15 v2 (20 vcpus, 140 GB memory) > "effective_cache_size" "105GB" "configuration file" > "effective_io_concurrency" "200" "configuration file" > "maintenance_work_mem" "2GB" "configuration file" > "max_paral

Re: Query slow for new participants

2019-02-25 Thread supp...@mekong.be
Hi, thank you for your reply. Yes, I will go through this page. Regards, Kim Op ma 25 feb. 2019 om 17:16 schreef Justin Pryzby : > On Mon, Feb 25, 2019 at 03:41:18AM -0700, Kim wrote: > > Is there any way how I can make the queries fast for new participants? > This > > is a big problem, because

Re: Query slow for new participants

2019-02-25 Thread Justin Pryzby
On Mon, Feb 25, 2019 at 03:41:18AM -0700, Kim wrote: > Is there any way how I can make the queries fast for new participants? This > is a big problem, because for new participants, speed is even more > important. > > Thank you for your help. Could you include information requested here ? https://

Query slow for new participants

2019-02-25 Thread Kim
Hello, I have an article query which returns articles enabled for a participant. Article table – Participant table – Table in between which stores the links between the Article and particitpant including characteristics such as enabled. It is possible to search on the articles by number, descripti