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 1qA55L-0002vU-7V for pgadmin-hackers@arkaria.postgresql.org; Fri, 16 Jun 2023 08:45: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 1qA55J-0005RV-QQ for pgadmin-hackers@arkaria.postgresql.org; Fri, 16 Jun 2023 08:45:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qA55J-0005RL-AV for pgadmin-hackers@lists.postgresql.org; Fri, 16 Jun 2023 08:45:33 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qA55E-002VA1-Gv for pgadmin-hackers@postgresql.org; Fri, 16 Jun 2023 08:45:31 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-39cf00a2ad2so414055b6e.1 for ; Fri, 16 Jun 2023 01:45:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686905128; x=1689497128; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZTw8IWW0afhb7T925wM7NTgrHLw5dsgu9ouNszgUc9o=; b=VneIFSzO6G0CHMAPj8XWPOjDapkfUM9sGC2OBzhFbZsYR6o9XsFjlQRoeZpFrm/5Rx 7KR5p2/cDWlbCa961t22bzkW2htYdhB2DTXoa2/lhJmemuzaVLZulNvgAhVJklABKAZK a2dYnUHH0B7yib3+qM4kUdLdwAvXwShowhF7qmtENNv/cB2P5FIap3Q36t1P5GCsyZPW afZFKHGsA4mmzuWJ20RD6Dc7PMANIt9eZynmuQ7eLvWeUMBHxdRQrW2A8oJK0XMedSpS n7tzOAn0YmeTK/v6inleKv0/pRYTABXMFHAd+grDKwljh2xvtOX/HLo9J5SAoi88TtzS +iyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686905128; x=1689497128; 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=ZTw8IWW0afhb7T925wM7NTgrHLw5dsgu9ouNszgUc9o=; b=C/iBtfGqFpKTy+3puuKU8CYt57SQJEM/whOsz8qBDycvzvk1qYfVZkYjKnjfjXEL30 Er6lNQ6Cnt6SrBmsbz9huMGwEZg9s7XFszJoNei/rfBv5KsVsdZKqjMdLeGeGZWOGVaK m/Qr4ugb8pZqn4XpXbH8FQ8oxlyRP9s9DG88jofl0rDt09LWCyJPsXwu29KYB7xQukeG L5a31kSffiHaX4Qy858Cxv0JZAmd71rfcjpva/9lBvAfRRge9jiNFADTJdQvNGu8eO0s SQMrmVq8BhJfZwfDnhrHqwPrUReKnIpedjfoU3gxKQgfDYPb9V7sxCgpDqy3F2SeNrKs AquQ== X-Gm-Message-State: AC+VfDyQ0RkFL82gFyCh06Y6YQgmUb2vOyIwy0tdxRHcOyiF+k1swAGM ziEgf9p6/jILxbr5uUrXeXZIRzbAJykB6+ug1mg/MdQzp8nJ6g== X-Google-Smtp-Source: ACHHUZ4wkFSQN27gHS6nu7zMA2sRiZHmzhpdpRdM99wO/I2ScG/x/lO2eyYH5GmnDvfbblADYuKgVFnzA0srWJvWF5A= X-Received: by 2002:a05:6808:219e:b0:39a:bb0e:3685 with SMTP id be30-20020a056808219e00b0039abb0e3685mr1786340oib.29.1686905127863; Fri, 16 Jun 2023 01:45:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sahil Harpal Date: Fri, 16 Jun 2023 14:15:14 +0530 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: Dave Page Cc: Khushboo Vashi , Aditya Toshniwal , Akshay Joshi , pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="000000000000ea8b0105fe3b3422" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ea8b0105fe3b3422 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > 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 or 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 eac= h >> parameter for 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). > > >> >> On Thu, Jun 15, 2023 at 3:22=E2=80=AFPM Dave Page wr= ote: >> >>> >>> >>> 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 for >>>> 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 grou= ping >>> 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 th= e >>> 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 t= hem. >>>>>>> >>>>>>> Design 1 - Using an additional new tab for system statistics >>>>>>> Design 2 - Added buttons to toggle between existing dashboard data >>>>>>> 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 "Sys= tem >>>>>> 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 dashboard. >>>>>>>> >>>>>>>> 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 wire= frame to >>>>>>>>> display system stats on the existing dashboard. >>>>>>>>> >>>>>>>>> I am open to hearing your thoughts and suggestions on the design. >>>>>>>>> >>>>>>>>> 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 > > --000000000000ea8b0105fe3b3422 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=3D""
I think combining R/W is fine, a= s long as it uses two scales in case the values are wildly different (which= is likely).

So should I combine all the paramet= ers (Total read/write operations, Total Bytes read/write, and time spent) i= n a single graph for one disk or just the total number of read/write operat= ions?
=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 T= hu, 15 Jun 2023 at 11:07, Khushboo Vashi <khushboo.vashi@enterprisedb.com&= gt; wrote:
Regarding I/O analysis, what would be more beneficial, combinin= g total read/total write etc., per disk OR Sahil doing a different graph fo= r each parameter=C2=A0for all the disks?

<= div>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).
=C2=A0

On Thu, Jun 15, 2023 at 3:22=E2=80= =AFPM Dave Page <= dpage@pgadmin.org> wrote:


On Thu, 15 Jun 2023 = at 09:55, Sahil Harpal <sahilharpal1234@gmail.com> wrote:
H= i Aditya,

Thank you for pointing this out. It would also= be more convenient for users to navigate to specific statistics easily.
So, can we finalise the following design?
- Single dashboard with b= uttons to toggle between General (existing graphs/stats) and System Statist= ics.

Why use buttons = and not tabs? Tabs are far more flexible as they can be re-arranged, docked= differently etc.
=C2=A0
- Clubbing OS, CPU, P= rocess, 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 grouping though. Maybe:

Summary (OS info, sys= tem 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, m= emory per process on the memory tab, etc..)


Thanks,
Sahil


3D""
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 t= abbed control. (Taking inspiration from the task manager).
It will reduce the network calls, clutt= ering and improve DOM performance.


On Thu, Jun 15, 2023 at 11:08=E2=80=AFAM Akshay Joshi = <aksh= ay.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<= /div>
Here are a few more designs that I have created based on the disc= ussion with my mentors. I would love to know your thoughts=C2=A0on them.=C2= =A0

Design 1 - Using an additional new tab for system sta= tistics
Design 2 - Added buttons to toggle between existing dashboard da= ta and system statistics.

=
=C2=A0 =C2=A0 I personally like Design 2 as we have only one main tab = "Dashboard" and then two sub-tabs "General"(Can be chan= ged) 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 glance, it looks good=C2=A0to me. Seems you have c= reated a new tab System Statistics instead of using the existing dashboard.= =C2=A0

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

I am working on pgadmi= n4 to let users see their system-level statistics on the dashboard. In this= mail, I've attached the wireframe to display system stats on the exist= ing dashboard.

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

Thanks,
Sahi= l
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

--000000000000ea8b0105fe3b3422--