Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qJ9Mz-0003eB-Sw for pgadmin-hackers@arkaria.postgresql.org; Tue, 11 Jul 2023 09:09:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qJ9Lz-0000cy-6b for pgadmin-hackers@arkaria.postgresql.org; Tue, 11 Jul 2023 09:08:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qJ9Ly-0000Rm-Sv for pgadmin-hackers@lists.postgresql.org; Tue, 11 Jul 2023 09:08:14 +0000 Received: from mail-oa1-x2d.google.com ([2001:4860:4864:20::2d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qJ9Lt-003Rn1-JN for pgadmin-hackers@postgresql.org; Tue, 11 Jul 2023 09:08:13 +0000 Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-1b449890ef5so4232726fac.1 for ; Tue, 11 Jul 2023 02:08:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1689066486; x=1691658486; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xup/FYWhMPxesWNdij6iWrAdZr2U/SisZnTEXsPj6hk=; b=UbK/6i2uLTVYmgcaGbg27Vq4KEmqLw7R6s9Rh93pa6ALwq1cdd51a9lw37ftxkXYSr EatHdCp9jK2KCIK7LLT1CPrwdeAeYxf3Cl0TtJvFT0tsCDZ2VDYgu0mLjh2j4QCwk0WE KL99v/mJEvoBlfPlJRicgrysrJ77Dq2fldj7TB0+A8IwdgLZ0guFmGpeVCn6W9bKDgOL ZQCyOuTQOlVh1I3ffkkz3/SEuC1vfn0dqrdq7WDegCtT6Tu/ylFispFojkoEfIp5BhCT Ks0GfVKgo5eksTup3w0FAkm+qmS/xgk2ITpqmOuCLWmMfMY/81fYa2NE0wF1sTLRaU7E vhcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689066486; x=1691658486; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xup/FYWhMPxesWNdij6iWrAdZr2U/SisZnTEXsPj6hk=; b=HUwKC9/Tvj+pyEYUvMXUlENYaJUCBJHdKsHsfXqkQSf+E/c0rzoLVrW5mTRc2yUJLc 5JPH98qtqVCRMv4MBZFROPhUpXWh4/nP5oddcOjDcqp/vi2N27aSP/A4AG4c0qR/TlEu fLjHbpooU4Rh1hOrfPn98xoeVP3xQodrP3dYqvhQbZjhgimnqEyM/ouuuaduLpv6ieiX Hr8YiAqjsrxWdgTSBEcVdgzYcOSelaPpsYvbX/1RCAiuq98y5YqV9BxrAgO4swMh9lnq ewfjYKRE+Ihl0OBvuxaMaMs3KSnjyeAZM3rfYwjz9jnjLzbPAmmMLY8/HBxWJOW/oMrS zMkw== X-Gm-Message-State: ABy/qLYejQw2oXBecmgkj/KNfgyERsx6yXFQilt8oN5/hgOSemdxU0aL InCQ21B23nbXf/7GpIyJ0O03/Y1iwDsk5mFaY/eO/RNQrbw2ag7z X-Google-Smtp-Source: APBJJlEROPVyGsBqowa9Opo0OoGY8HC4M1SuC0eOAXwM+Bhai2f5jhMlov8H9U1xQBPRDRqySRhPC82x/cZKNweVESM= X-Received: by 2002:a05:6870:b506:b0:1b0:2b1b:197 with SMTP id v6-20020a056870b50600b001b02b1b0197mr18861911oap.47.1689066486607; Tue, 11 Jul 2023 02:08:06 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aditya Toshniwal Date: Tue, 11 Jul 2023 14:37:30 +0530 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: Sahil Harpal Cc: Ashesh Vashi , Dave Page , Akshay Joshi , Khushboo Vashi , pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="000000000000efcb950600326f4d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000efcb950600326f4d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Sahil, On Tue, Jul 11, 2023 at 2:29=E2=80=AFPM Sahil Harpal wrote: > On Tue, 11 Jul 2023 at 12:04, Ashesh Vashi > wrote: > >> Try preloading the extension in the PostgreSQL server. >> e.g. Add this extension in the 'shared_preload_libraries' in >> postgresql.conf. >> >> Reference: https://pgpedia.info/s/shared_preload_libraries.html >> > Thank you, Ashesh! I will try this and provide you with an update. > > On Tue, 11 Jul 2023 at 12:39, Aditya Toshniwal < > aditya.toshniwal@enterprisedb.com> wrote: > >> Hi Sahil, >> >> Just to mention, make sure you're not using any chart component other >> than StreamingChart if the data is frequently updated. >> We have faced performance issues for continuously updating charts with >> Chart.js. >> > > Also, as Aditya has mentioned, yeah, it will definitely affect the > performance, as re-rendering the charts would be costly. So, would love t= o > know suggestions for Disk info and Process info, as we have decided to us= e > pie and bar charts over there. > Disk info doesn't need to be updated live. You can update it once on every tab change. I feel process info should be a bar chart. The categories are fixed in number and we can use StreamingChart for bar chart. > Either we can reload the charts only when the tab changes, or we can use > StreamingChart for them too? > > Also, currently, StreamingChart is not formatting the axis values and > takes much space in case of larger values eg. memory_usage, handle_count > etc. Can we add a custom formatter for y-axis values? I have attached the > images for the same. > Sure, you can tweak StreamingChart. > --=20 Thanks, Aditya Toshniwal pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* "Don't Complain about Heat, Plant a TREE" --000000000000efcb950600326f4d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Sahil,

On Tue, Jul 11, 2023 at 2:29=E2= =80=AFPM Sahil Harpal <sahi= lharpal1234@gmail.com> wrote:
On Tue, 11 Jul 2023 = at 12:04, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Try preloading = the extension in the PostgreSQL server.
e.g.=C2=A0 Add this extension in= the 'shared_preload_libraries' in postgresql.conf.

Referenc= e:=C2=A0https://pgpedia.info/s/shared_preload_libr= aries.html
Thank you, Ashesh! I will= try this and provide you with an update.

On Tue, 11 Jul 2023 at 12:39, Aditya Tosh= niwal <aditya.toshniwal@enterprisedb.com> wrote:
Hi Sahil,=C2=A0

= Just to mention, make sure you're not using any chart component other t= han StreamingChart if the data is frequently updated.
We have faced performance issues for continuo= usly updating charts with Chart.js.

= Also, as Aditya has mentioned, yeah, it will definitely affect the performa= nce, as re-rendering the charts would be costly. So, would love to know=C2= =A0suggestions for Disk info and Process info, as we have decided to use pi= e and bar charts over there.
Disk info doesn= 't need to be updated live. You can update it once on every tab change.= =C2=A0I feel process info should be a bar chart. The categories are fixe= d in number and we can use StreamingChart for bar chart.
Either we can reload the charts only when the tab changes, or = we can use StreamingChart for them too?

Also, currently, Stream= ingChart is not formatting the axis values and takes much space in case of = larger values eg. memory_usage, handle_count etc. Can we add a custom forma= tter for y-axis values? I have attached the images for the same.=C2=A0 =C2= =A0
Sure, you can tweak StreamingChart.=C2=A0
3D""


--
Thanks,
Aditya Toshniwal
pgAdmin Hacker=C2=A0| Sr. Software Architect=C2=A0| enterprisedb.com