Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZHhW9-0000IS-BP for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Jul 2015 00:04:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZHhW8-000517-H2 for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Jul 2015 00:04:12 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZHhUq-0003XM-VU for pgsql-hackers@postgresql.org; Wed, 22 Jul 2015 00:02:53 +0000 Received: from 01.zmailcloud.com ([192.198.85.104] helo=mx-out-1.zmailcloud.com) by makus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1ZHhUn-0000rN-Nz for pgsql-hackers@postgresql.org; Wed, 22 Jul 2015 00:02:51 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 96147564020; Tue, 21 Jul 2015 19:02:46 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 7AE5DA0499; Tue, 21 Jul 2015 19:02:46 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnM_EvNlMYTT; Tue, 21 Jul 2015 19:02:46 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 4AED1A04B0; Tue, 21 Jul 2015 19:02:46 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 22339A0499; Tue, 21 Jul 2015 19:02:46 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RapSTF7af5R9; Tue, 21 Jul 2015 19:02:46 -0500 (CDT) Received: from [192.168.47.106] (50-1-62-61.dsl.dynamic.fusionbroadband.com [50.1.62.61]) by smtp-out-1.01.com (Postfix) with ESMTPSA id 8736EA04A7; Tue, 21 Jul 2015 19:02:45 -0500 (CDT) Message-ID: <55AEDDA4.8020009@agliodbs.com> Date: Tue, 21 Jul 2015 17:02:44 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Fabien COELHO , Robert Haas CC: PostgreSQL Developers Subject: Re: pgbench stats per script & other stuff References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 07/21/2015 09:29 AM, Fabien COELHO wrote: > Maybe -f file.sql:weight (yuk from my point of view, but it can be done > easily). Maybe it's past time for pgbench to have a config file? Given that we want to define some per-workload options, the config file would probably need to be YAML or JSON, e.g.: pgbench --config=workload1.pgb workload1.pgb ------------- database: bench port: 5432 host: localhost user: josh clients : 16 threads : 4 response-times : on stats-level: script script1: file: script1.bench weight: 3 script2: file: script2.bench weight: 1 the above would execute a pgbench with 16 clients, 4 threads, "script1" three times as often as script2, and report stats at the script (rather than SQL statement) level. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers