Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1alhxL-0000GX-2a for pgsql-performance@arkaria.postgresql.org; Thu, 31 Mar 2016 19:08:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1alhxK-000833-LH for pgsql-performance@arkaria.postgresql.org; Thu, 31 Mar 2016 19:08:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1alhxJ-00081e-TF for pgsql-performance@postgresql.org; Thu, 31 Mar 2016 19:08:34 +0000 Received: from mail.srv.pl ([2001:1a68:0:c::4a]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1alhxG-0005IP-Oi for pgsql-performance@postgresql.org; Thu, 31 Mar 2016 19:08:33 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=srv.pl; s=dkim; h=Content-Transfer-Encoding:Mime-Version:Content-Type:Date:To:From:Subject:Message-ID; bh=Itvt6pP+kuAQxTJpkCYRC06zn8CzwWMnbAfbrWjo2cY=; b=wZ/ld1cWQqDi6/ajh4siPB31Jqhy9qURxYX5IzzvaxIVZYCEGnMO/TLXAWHr1LJxakRN0FTjOmDjCLerU3UsC5/5fkcxoZcaI0nOsHepmYWM4IACkz3gWGP7B9dAkxqVGTFQfYxBEC0HdDAcuZfGDAijNTlZ0BHNXpcmNHHzsbg=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bodygloveoptrix.pl; s=dkim; h=Content-Transfer-Encoding:Mime-Version:Content-Type:Date:To:From:Subject:Message-ID; bh=Itvt6pP+kuAQxTJpkCYRC06zn8CzwWMnbAfbrWjo2cY=; b=SLP8HDwYfltsI6H3RVpNUD/hULhtcbHJ5Tpb8qBcPPeLIsPVaMxuXwiesSkHs/erflGtjRhgNB2MqOJGPYg1+KSXf43BTtNwubwBjS+c8BbimI+SV1iywTN9wefGPri2JHEsZk9+s0P4v8eAYQ4DzRuwcthPCY8a9OCZKozW9zc=; Message-ID: <1459451286.26406.16.camel@sem-jarek-01.prv> Subject: Big number of connections From: Jarek To: pgsql-performance@postgresql.org Date: Thu, 31 Mar 2016 21:08:06 +0200 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: -2.9 X-Spam-Level: -- X-Pg-Spam-Score: -2.9 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Hello! We are going to build system based on PostgreSQL database for huge number of individual users (few thousands). Each user will have his own account, for authorization we will use Kerberos (MIT or Windows). Most of users will have low activity, but for various reasons, connection should be open all the time. I'd like to know what potential problems and limitations we can expect with such deployment. During preliminary testing we have found that for each connection we need ~1MB RAM. Is there any way to decrease this ? Is there any risk, that such number of users will degrade performance ? I'll be happy to hear any remarks and suggestions related to design, administration and handling of such installation. best regards Jarek -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance