Thank you for advice.
1)
First off all, we use java app with jdbc driver wich can pool connection,
thats why i don't think that this is good decision to put one more
pooler between
app and DB. May be someone have an experience with pgbouncer and jdbc and
could give a good advice with advantage an
On Tue, Nov 5, 2013 at 6:27 PM, Jan Walter wrote:
> On 5.11.2013 23:19, Merlin Moncure wrote:
> On Tue, Nov 5, 2013 at 3:52 PM, Jan Walter wrote:
> On 5.11.2013 20:51, Merlin Moncure wrote:
> On Tue, Nov 5, 2013 at 11:30 AM, Merlin Moncure wrote:
> On Tue, Nov 5, 2013 at 6:25 AM, Jan Walter wro
On Wed, Nov 6, 2013 at 1:53 AM, Евгений Селявка wrote:
> Thank you for advice.
>
> 1)
> First off all, we use java app with jdbc driver wich can pool connection,
> thats why i don't think that this is good decision to put one more pooler
> between app and DB. May be someone have an experience with
On Sun, Nov 3, 2013 at 4:05 PM, Caio Casimiro wrote:
> System Information:
> OS: Slackware 14.0
> Postgresql Version: 9.3 Beta2
This probably doesn't have anything to do with your problem, but it's
long past time to migrate from the beta to the production 9.3.
merlin
--
Sent via pgsql-perform
As a followup to my previous message, here's a response curve on a 48
core server I used at my last job.
https://picasaweb.google.com/lh/photo/aPYHPWPivPsS79fG3AKtZNMTjNZETYmyPJy0liipFm0?feat=directlink
Note the peak at around 38 to 48 cores. This is the sweetspot on this
server for connections.
Also also, the definitive page for postgres and dirty pages etc is here:
http://www.westnet.com/~gsmith/content/linux-pdflush.htm
Not sure if it's out of date with more modern kernels. Maybe Greg will chime in.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To ma
On Mon, Nov 4, 2013 at 12:44 PM, Caio Casimiro wrote:
> Thank you very much for your answers guys!
>
>
> On Mon, Nov 4, 2013 at 5:15 PM, Jeff Janes wrote:
>
>> On Sun, Nov 3, 2013 at 2:05 PM, Caio Casimiro
>> wrote:
>>
>>>
>>> SELECT tt.tweet_id, tt.topic, tt.topic_value
>>> FROM tw
Thank you for your considerations Jeff. Actually I'm running an experiment
proposed by other researchers to evaluate a recommendation model.
My database is composed only by old tweets. In this experiment the
recommendation model is evaluated in a daily basis, and that's the reason
the query collect
On Sat, Nov 2, 2013 at 1:54 PM, Евгений Селявка wrote:
> Please help with advice!
>
> Server
> HP ProLiant BL460c G1
>
> Architecture: x86_64
> CPU op-mode(s):32-bit, 64-bit
> Byte Order:Little Endian
> CPU(s):8
> On-line CPU(s) list: 0-7
> Thread(s)
