Re: Are bitmap index scans slow to start?

From: "Carlo Stonebanks" <stonec(dot)register(at)sympatico(dot)ca>
To: "'Jeff Janes'" <jeff(dot)janes(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Are bitmap index scans slow to start?
Date: 2013-02-28 05:12:48
Message-ID: 024301ce1572$3fea5560$bfbf0020$@sympatico.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

<<

I had thought you were saying that any one ETL procedure into one database
used 14 concurrent threads. But really, each ETL procedure is
single-threaded, and there can be up to 5 (or theoretically up to 14) of
them running at a time into different databases?
>>

Sorry, just caught this.

Your first interpretation was correct. Each DB runs an ETL that can have up
to 14 concurrent threads. I don't think the number should be that high, but
the engineering team insists the load time is better than fewer threads
running faster.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Ao Jianwang 2013-02-28 15:11:16 SELECT is slow on smaller table?
Previous Message Josh Berkus 2013-02-27 23:07:27 Re: Server stalls, all CPU 100% system time