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 1qBFwk-00025i-J5 for pgadmin-hackers@arkaria.postgresql.org; Mon, 19 Jun 2023 14:33:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qBFwj-0001yz-FJ for pgadmin-hackers@arkaria.postgresql.org; Mon, 19 Jun 2023 14:33:33 +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 1qBFwi-0001yq-Vh for pgadmin-hackers@lists.postgresql.org; Mon, 19 Jun 2023 14:33:33 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qBFwf-003RIF-EM for pgadmin-hackers@postgresql.org; Mon, 19 Jun 2023 14:33:32 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-988f066f665so53785866b.2 for ; Mon, 19 Jun 2023 07:33:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1687185208; x=1689777208; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xr7RvEQLWCG4JNnGiY+czd7JHQxeUVgmYkPSEvb/jv0=; b=A8ldqY1LgkuHL7535zRMLYMfYq+tYmZaQ3oAaDv7BgTnMRgsj06bVqxxaiPBc36Cgn U6Q2eSkks7+wjyl3U+2X5uY2aYBtV22uHothRBdhdfmOf75k7pOOqZzGRIgMQ0lpiaZK l7XDhNv2WSJ5eEZvgrqqx7WCMin+KLfKp3hB40Ie0zEt/boPYzIL+1Wyo1+Utv77NUYD iYhbSYqhj0pX9/3R0OIw+wovp+G7L3y2ww1JhETg6MDX2kWAmChPxEeV661gg1URb4hd XJVYgYPKOQhh+2pTOfq0EFZZh+DIQRcCrLyyepxOFnMcCQywbBCLZMXHNbFtA+dkMMZ0 xPMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687185208; x=1689777208; 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=xr7RvEQLWCG4JNnGiY+czd7JHQxeUVgmYkPSEvb/jv0=; b=OZH3VKSGSAics1aC4YRISkBipvzfw2fVUuJYPL0Qh1SUriKJR8H7MgQT4kiGMCtuuM 4QV2Cyb2xIXrt5fOBAG5yg/Y2Ako9Dpq8Bmpai1jmznK30sO7e1QZ2xRI2Ad89by9FwV vPdIKPTGkZH5A2EGPh8Sb/5kK1KccNCYPwMBuc4yTGxsW2M1s/hnqMIYstnltThEJVIr KpQV7/8m54Yt3qPM4+motiXu1OKSbAoa5yXjopO3oCb+lv3b4VvMyh7xgkFIiUfe+5ak 18uv2yZA1kX8OO0DYQ/9h9nm434emgQh94CEVTmKMCnpJ98Mus4TFGnSVFoHWmSsZafG teRw== X-Gm-Message-State: AC+VfDzmid53RD2llhqLERF6Vx862+I1eTQQUKThusioTl3p0e3gSNwN 4i6nUrrrbdHJ7BqWbb6rkTf1T2ovvTSPZ5Hl7cZcdLc1D6/gRASLJ8k= X-Google-Smtp-Source: ACHHUZ5eClUlJdawRhYCzpKLxLQ71aCuBbPGHdGSy+Ce5rub+WT3vhu76gmznxU3dNX5sccnqfZ4Uwc9fJQo1YUySgc= X-Received: by 2002:a17:907:e92:b0:988:9b29:564c with SMTP id ho18-20020a1709070e9200b009889b29564cmr2862272ejc.59.1687185208528; Mon, 19 Jun 2023 07:33:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Mon, 19 Jun 2023 15:33:17 +0100 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: Sahil Harpal Cc: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="00000000000006669305fe7c6b52" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000006669305fe7c6b52 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 19 Jun 2023 at 15:30, Sahil Harpal wrote: > On Fri, 16 Jun 2023 at 14:15, Sahil Harpal > wrote: > >> [image: image.gif] >> >>> I think combining R/W is fine, as long as it uses two scales in case th= e >>> values are wildly different (which is likely). >> >> >> So should I combine all the parameters (Total read/write operations, >> Total Bytes read/write, and time spent) in a single graph for one disk o= r >> just the total number of read/write operations? >> > > Could you please also clarify this? > Don't combine ops/time/bytes etc, but you can combine read/write, input/output etc. as we do on the existing graphs. > > > On Fri, 16 Jun 2023 at 14:15, Sahil Harpal > wrote: > >> I think combining R/W is fine, as long as it uses two scales in case the >>> values are wildly different (which is likely). >> >> >> So should I combine all the parameters (Total read/write operations, >> Total Bytes read/write, and time spent) in a single graph for one disk o= r >> just the total number of read/write operations? >> [image: Mailtrack] >> Sender >> notified by >> Mailtrack >> 16/06/23, >> 14:14:28 >> >> On Thu, 15 Jun 2023 at 16:27, Dave Page wrote: >> >>> >>> >>> On Thu, 15 Jun 2023 at 11:07, Khushboo Vashi < >>> khushboo.vashi@enterprisedb.com> wrote: >>> >>>> Regarding I/O analysis, what would be more beneficial, combining total >>>> read/total write etc., per disk OR Sahil doing a different graph for e= ach >>>> parameter for all the disks? >>>> >>> >>> I think combining R/W is fine, as long as it uses two scales in case th= e >>> values are wildly different (which is likely). >>> >>> >>>> >>>> On Thu, Jun 15, 2023 at 3:22=E2=80=AFPM Dave Page = wrote: >>>> >>>>> >>>>> >>>>> On Thu, 15 Jun 2023 at 09:55, Sahil Harpal >>>>> wrote: >>>>> >>>>>> Hi Aditya, >>>>>> >>>>>> Thank you for pointing this out. It would also be more convenient fo= r >>>>>> users to navigate to specific statistics easily. >>>>>> >>>>>> So, can we finalise the following design? >>>>>> - Single dashboard with buttons to toggle between General (existing >>>>>> graphs/stats) and System Statistics. >>>>>> >>>>> >>>>> Why use buttons and not tabs? Tabs are far more flexible as they can >>>>> be re-arranged, docked differently etc. >>>>> >>>>> >>>>>> - Clubbing OS, CPU, Process, Disk and I/O in tabbed control. >>>>>> >>>>> >>>>> I think the current design has too much on one big page, so yes, I'd >>>>> want to see those split up onto different tabs. Not sure about the gr= ouping >>>>> though. Maybe: >>>>> >>>>> Summary (OS info, system specs etc) >>>>> CPU >>>>> Memory >>>>> Storage (including I/O) >>>>> >>>>> Process info would be included on each tab as related to that tab's >>>>> content - e.g. CPU per process on the CPU tab, memory per process on = the >>>>> memory tab, etc..) >>>>> >>>>> >>>>>> Thanks, >>>>>> Sahil >>>>>> >>>>>> >>>>>> On Thu, 15 Jun 2023 at 11:21, Aditya Toshniwal < >>>>>> aditya.toshniwal@enterprisedb.com> wrote: >>>>>> >>>>>>> Hi Sahil, >>>>>>> >>>>>>> I would suggest club OS, CPU, Process, Disk and I/O in a tabbed >>>>>>> control. (Taking inspiration from the task manager). >>>>>>> It will reduce the network calls, cluttering and improve DOM >>>>>>> performance. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 15, 2023 at 11:08=E2=80=AFAM Akshay Joshi < >>>>>>> akshay.joshi@enterprisedb.com> wrote: >>>>>>> >>>>>>>> Hi Sahil >>>>>>>> >>>>>>>> On Thu, Jun 15, 2023 at 1:42=E2=80=AFAM Sahil Harpal < >>>>>>>> sahilharpal1234@gmail.com> wrote: >>>>>>>> >>>>>>>>> Thank you, Akshay, for your feedback. >>>>>>>>> Here are a few more designs that I have created based on the >>>>>>>>> discussion with my mentors. I would love to know your thoughts on= them. >>>>>>>>> >>>>>>>>> Design 1 - Using an additional new tab for system statistics >>>>>>>>> Design 2 - Added buttons to toggle between existing dashboard dat= a >>>>>>>>> and system statistics. >>>>>>>>> >>>>>>>> >>>>>>>> I personally like Design 2 as we have only one main tab >>>>>>>> "Dashboard" and then two sub-tabs "General"(Can be changed) and "S= ystem >>>>>>>> Statistics". >>>>>>>> >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Sahil >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, 14 Jun 2023 at 10:12, Akshay Joshi < >>>>>>>>> akshay.joshi@enterprisedb.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Sahil >>>>>>>>>> >>>>>>>>>> At first glance, it looks good to me. Seems you have created a >>>>>>>>>> new tab System Statistics instead of using the existing dashboar= d. >>>>>>>>>> >>>>>>>>>> On Tue, Jun 13, 2023 at 4:27=E2=80=AFPM Sahil Harpal < >>>>>>>>>> sahilharpal1234@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Dear all, >>>>>>>>>>> >>>>>>>>>>> I am working on pgadmin4 to let users see their system-level >>>>>>>>>>> statistics on the dashboard. In this mail, I've attached the wi= reframe to >>>>>>>>>>> display system stats on the existing dashboard. >>>>>>>>>>> >>>>>>>>>>> I am open to hearing your thoughts and suggestions on the desig= n. >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Sahil >>>>>>>>>>> >>>>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks, >>>>>>> Aditya Toshniwal >>>>>>> pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* >>>>>>> >>>>>>> "Don't Complain about Heat, Plant a TREE" >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> Dave Page >>>>> Blog: https://pgsnake.blogspot.com >>>>> Twitter: @pgsnake >>>>> >>>>> EDB: https://www.enterprisedb.com >>>>> >>>>> >>> >>> -- >>> Dave Page >>> Blog: https://pgsnake.blogspot.com >>> Twitter: @pgsnake >>> >>> EDB: https://www.enterprisedb.com >>> >>> --=20 Dave Page Blog: https://pgsnake.blogspot.com Twitter: @pgsnake EDB: https://www.enterprisedb.com --00000000000006669305fe7c6b52 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, 19 Jun 2023 at 15:30, Sahil H= arpal <sahilharpal1234@gmai= l.com> wrote:
3D""
On Fri, 16 Jun 2023 at 14:15, Sahil Harpal <sahilharpal1234@gm= ail.com> wrote:
3D"image.gif"
I think combini= ng R/W is fine, as long as it uses two scales in case the values are wildly= different (which is likely).

So should I combine all the par= ameters (Total read/write operations, Total Bytes read/write, and time spen= t) in a single graph for one disk or just the total number of read/write op= erations?

<= div dir=3D"ltr">Could you please also clarify this?

Don't combine ops/time/bytes etc, but you ca= n combine read/write, input/output etc. as we do on the existing graphs.
=C2=A0


On Fri, 16 Jun 2023 at 14:15, Sahil Harpal <sahilharpal1234@g= mail.com> wrote:
3D""
I think combining R/W is fine, as long as it uses two scales= in case the values are wildly different (which is likely).

So should I combine all the parameters (Total read/write operat= ions, Total Bytes read/write, and time spent) in a single graph for one dis= k or just the total number of read/write operations?
=20
3D"Mailtrack" Sender notified = by
Mailtrack =20 		16/06/23, 14:1= 4:28 =20

On Thu, 15 Jun 2023 at 16:27, Dave Page <dpage@pgadmin.org> wrote:


On Thu, 15 Jun 2023= at 11:07, Khushboo Vashi <khushboo.vashi@enterprisedb.com> wrote:
<= /div>
Regarding I/O analysis, what would b= e more beneficial, combining total read/total write etc., per disk OR Sahil= doing a different graph for each parameter=C2=A0for all the disks?

I think combining R/W is fine, as long as it= uses two scales in case the values are wildly different (which is likely).=
=C2=A0

On Thu, Jun 15, 2023 at 3:22=E2=80=AFPM D= ave Page <dpage@p= gadmin.org> wrote:


On Thu, 15 Jun 2023 at 09:55, Sahil Harpal <sahilharpal1234@gmail.co= m> wrote:
Hi Aditya,

Thank you for pointing this out. It would a= lso be more convenient for users to navigate to specific statistics easily.=

So, can we finalise the following design?
- Single dashboard wit= h buttons to toggle between General (existing graphs/stats) and System Stat= istics.

Why use butto= ns and not tabs? Tabs are far more flexible as they can be re-arranged, doc= ked differently etc.
=C2=A0
- Clubbing OS, CPU, Process, Disk and I/O in tabbed= control.

I think the cur= rent design has too much on one big page, so yes, I'd want to see those= split up onto different tabs. Not sure about the grouping though. Maybe:

Summary (OS info, system specs etc)
CPU
Memory
Storage (including I/O)

= Process info would be included on each tab as related to that tab's con= tent - e.g. CPU per process on the CPU tab, memory per process on the memor= y tab, etc..)


Thanks,
Sahil

=
3D""
On Thu, 15 Jun 20= 23 at 11:21, Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wro= te:
Hi Sahil,

I would suggest= club OS, CPU, Process, Disk and I/O in a tabbed control. (Taking inspirati= on from the task manager).
It will reduce the network calls, cluttering and improve DOM performance= .


On Thu, Jun = 15, 2023 at 11:08=E2=80=AFAM Akshay Joshi <akshay.joshi@enterprisedb.com>= wrote:
Hi=C2= =A0Sahil

On Thu, Jun 15, 2023 at 1:42=E2=80=AFAM Sahil Harpal <sahilharpal1234@gmail.= com> wrote:
Thank you, Akshay, for your feedback.=C2=A0
Here are a f= ew more designs that I have created based on the discussion with my mentors= . I would love to know your thoughts=C2=A0on them.=C2=A0

= Design 1 - Using an additional new tab for system statistics
Design 2 - = Added buttons to toggle between existing dashboard data and system statisti= cs.

=C2=A0 =C2=A0 I p= ersonally like Design 2 as we have only one main tab "Dashboard" = and then two sub-tabs "General"(Can be changed) and "System = Statistics".=C2=A0=C2=A0

Thanks,
Sahil



3D""
On Wed, 14 Jun 2023 = at 10:12, Akshay Joshi <akshay.joshi@enterprisedb.com> wrote:
Hi=C2=A0Sahil

At first g= lance, it looks good=C2=A0to me. Seems you have created a new tab System St= atistics instead of using the existing dashboard.=C2=A0

On Tue, Jun 13= , 2023 at 4:27=E2=80=AFPM Sahil Harpal <sahilharpal1234@gmail.com> wrote:
=
Dear all,

I am w= orking on pgadmin4 to let users see their system-level statistics on the da= shboard. In this mail, I've attached the wireframe to display system st= ats on the existing dashboard.

I am open to hearing your = thoughts and suggestions on the design.

Thanks= ,
Sahil
3D""


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

--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
=
EDB: https:/= /www.enterprisedb.com



--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
=
EDB: https:/= /www.enterprisedb.com



--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
=
EDB: https:/= /www.enterprisedb.com

--00000000000006669305fe7c6b52--