Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e70of-0004H9-Ms for pgsql-performance@arkaria.postgresql.org; Tue, 24 Oct 2017 15:08:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e70of-0005io-9Z for pgsql-performance@arkaria.postgresql.org; Tue, 24 Oct 2017 15:08:29 +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 1e70mt-0001Ct-4D for pgsql-performance@postgresql.org; Tue, 24 Oct 2017 15:06:39 +0000 Received: from mail-wm0-x22c.google.com ([2a00:1450:400c:c09::22c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e70mo-0004YZ-Cv for pgsql-performance@postgresql.org; Tue, 24 Oct 2017 15:06:38 +0000 Received: by mail-wm0-x22c.google.com with SMTP id r68so17009613wmr.3 for ; Tue, 24 Oct 2017 08:06:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UdzqeXeiPwYUhYm7unjDWAePutlC+x6anr1viBaUjeM=; b=DG4S8qD15rxp205rNpG0tcoqni875fsjyO6BYBQ8MgiH+htjuBq02cSmfypyN4orTO F0XW9VVvco5pwJbRMniZ0kRRAKik91IyFF3+iDMHwBotsHMlHEf9tI7QNsw2RbXPN2qE E0plB7LMlPrh6u44ts88dNU66LB7Wjk7xyQZvB9/beeuvrVAq0QqrtC5jzNShoXhKCBg z5lkJB4l6wHbx4i9etOLPh/yTVEBywcYJiQlm6thuV5+Cf2L30yyJwAvxG/oxguesDgF mWdMtqryxk47qB7DjELnIUA0I/IVM+u0MVrvSicTBxk70S6xMh2MM1yxTpFbMqpFm+rT z5Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UdzqeXeiPwYUhYm7unjDWAePutlC+x6anr1viBaUjeM=; b=tplGSNGI5OBF2RqUMLfqEG+jLPwV3otwkXvXZzQyLBX12XPq6uvcWOh8anzGLmPjBh Lk/JCsCWZ0OesC/ZcqpMFExuSrav4f6Y9ie2elWw4ck9ewXlLPBecobiDh9DxYvLw/Gd PvzzstltV5NmwdRTkmpXdFyvf7kpWXsBCZy+ep8rAG8o77M4BkBE7/y0tB9qSZSp3HM2 f1vcIqi99U9zic/RmHFYaRwfEDB5YaDZUihnZ/foAiD0NmOP95Y1Z53UFJNacZgm4mqa /eh0X+Ybu9hv4afun/B1xmjJuwImSylgRTMoYm4koa/+9CQiEmdr+vFn9cWa4yTyLuP1 Ssng== X-Gm-Message-State: AMCzsaV8vBEgf29ADwYNzO42lmNO1+uIiahpYW7dsFdPdJJ30iWtvmXN 4NlFituC+oA9qpWzROxGIWUosYkvRe4nPj8iKO50FEhm X-Google-Smtp-Source: ABhQp+RejkSqg/o7UvqZRyUJulinOB6z20BugZdozrjFQfZibnVh57rCudlcvQp+Zka0AMkhtVCw6TGaL2PpDohCIV4= X-Received: by 10.28.167.77 with SMTP id q74mr7864715wme.53.1508857593686; Tue, 24 Oct 2017 08:06:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.197.78 with HTTP; Tue, 24 Oct 2017 08:06:33 -0700 (PDT) In-Reply-To: <1508856671425-0.post@n3.nabble.com> References: <1508790557217-0.post@n3.nabble.com> <1508856671425-0.post@n3.nabble.com> From: Purav Chovatia Date: Tue, 24 Oct 2017 20:36:33 +0530 Message-ID: Subject: Re: postgresql tuning with perf To: legrand legrand Cc: pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary="001a114b83f4e36fff055c4c48fd" 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 --001a114b83f4e36fff055c4c48fd Content-Type: text/plain; charset="UTF-8" We record like this: perf record -g -u enterprisedb We report like this: perf report -g -i perf.data Is this what you were looking for? Sorry, we are new to perf so we might be sharing something different as compared to what you asked. We already shared the SP code in the original post. Thanks On 24 October 2017 at 20:21, legrand legrand wrote: > Please share how you monitor your perfs. > > At less duration for each plpgsql proc / oracle proc. > Please share your plpgsql code, and commit strategy. > > (for support with edb please check with your contract manager) > > > > -- > Sent from: http://www.postgresql-archive.org/PostgreSQL-performance- > f2050081.html > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > --001a114b83f4e36fff055c4c48fd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
We record like this:=C2=A0perf record=C2=A0 -g -u enterpri= sedb
We report like this:=C2=A0perf report -g -i perf.data
Is this what you were looking for? Sorry, we are new to perf s= o we might be sharing something different as compared to what you asked.

We already shared the SP code in the original post.<= /div>

Thanks

<= div class=3D"gmail_quote">On 24 October 2017 at 20:21, legrand legrand <legrand_legrand@hotmail.com> wrote:
Please share how you monitor your perfs.

At less duration for each plpgsql proc / oracle proc.
Please share your plpgsql code, and commit strategy.

(for support with edb please check with your contract manager)



--
Sent from: http://www.postgres= ql-archive.org/PostgreSQL-performance-f2050081.html


--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pe= rformance

--001a114b83f4e36fff055c4c48fd--