From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Bottlenecks with large number of relation segment files |
Date: | 2013-08-05 06:23:19 |
Message-ID: | CA+HiwqEmgaVoMwSFcXOoxNB-bnGHaEwEPwrs5R+do5Uzt2G-3Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Hello,
I am looking the effect of having large number of relation files under
$PGDATA/base/ (for example, in cases where I choose lower segment size
using --with-segsize). Consider a case where I am working with a large
database with large relations, for example a database similar in size
to what "pgbench -i -s 3500" would be.
May the routines in fd.c become bottleneck with a large number of
concurrent connections to above database, say something like "pgbench
-j 8 -c 128"? Is there any other place I should be paying attention
to?
--
Amit Langote
From | Date | Subject | |
---|---|---|---|
Next Message | KONDO Mitsumasa | 2013-08-05 08:01:10 | Re: [GENERAL] Bottlenecks with large number of relation segment files |
Previous Message | Thomas Kellerer | 2013-08-05 06:21:50 | Re: Postgres 9.2.4 for Windows (Vista) Dell Vostro 400, re-installation failure PLEASE CAN SOMEONE HELP!! (nearly fixed) |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-08-05 06:27:22 | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Previous Message | Etsuro Fujita | 2013-08-05 06:23:17 | Re: query_planner() API change |