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 1qBFu5-0001zE-Pz for pgadmin-hackers@arkaria.postgresql.org; Mon, 19 Jun 2023 14:30:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qBFu4-0000z0-1Z for pgadmin-hackers@arkaria.postgresql.org; Mon, 19 Jun 2023 14:30:48 +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 1qBFu3-0000yr-Fc for pgadmin-hackers@lists.postgresql.org; Mon, 19 Jun 2023 14:30:47 +0000 Received: from mail-pj1-x102a.google.com ([2607:f8b0:4864:20::102a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qBFu0-0034JV-BP for pgadmin-hackers@postgresql.org; Mon, 19 Jun 2023 14:30:46 +0000 Received: by mail-pj1-x102a.google.com with SMTP id 98e67ed59e1d1-25e83254ff5so2267377a91.1 for ; Mon, 19 Jun 2023 07:30:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687185043; x=1689777043; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vXtjWrvkuJBSopbV5HP2UYGBZ83L+zYxeyOAPJmCays=; b=X14M54eZ+xq2R/fOe/TKUYAyQyfXuY3HHDq6Sj61uC2zi1FJ1/AYdxNbbxibb01QY7 6St5UzdQOhP+cI1s+0JsU0u1Pljik+7lgi88Zh7IyqmtcxceGUw+O/SdKcwxFYvRwWRX UjrZsNul05gqbNTjxJcosocVn3FZLQPlio4Mym8m4JZ4PIpsbQA1ggD8z1yyc5XeZst0 4HTZ+JhPJ8VNUe7DhBsAPTByfQd2Uf6AukCk7nbjO9Jtp/slu3oPlAkogwinGbGz+rYF bvSixt5bA/JqJyrbR9aSwJgu5XVAAI89segVVDzRaY7TC/X0EJAXFiju62fB9osdwZky T/Aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687185043; x=1689777043; 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=vXtjWrvkuJBSopbV5HP2UYGBZ83L+zYxeyOAPJmCays=; b=NQVQHQ/SKpthfJInTANIMV3kYqMG+sHZjEGNRIzEYCkCEAZvnr1WPLpwRrQ0LhlQXI i60WT5rswXQfZ6EYgYpwveJSSNGn1URfOiwJDMA4X0QYANU0l4cGdksJ6ZPDwdBSkYU4 LdZeaxHTLn/5vHIbjCFAPeuZulqc6iKyuVDvCP5zCFePSivI/CZvzf1WOExKyvOOSF4g mC0+hItFGrY8qJgc5hvoEC8nURHkJe2ZErGbjkkMIe6Gqk0TH2yNx5ezTQOj8FzNlJrD AJkxbuH1XGprpsLPgi5fqv9uZ2VQFK99ToaggnejFmKPn0wxXj9zgOCkpbrEQ87Aj9pD y51w== X-Gm-Message-State: AC+VfDzbB2ZPmNoRF7rpAhwkF71rpSKbK5t9Zcq+aOqWXBQBcjeQggKN YDyEW43W0hGuF8B6a54+twXiTud/KaRBiD7neo/szECanBQ= X-Google-Smtp-Source: ACHHUZ7/PhfjVYpNVYpJ+BD4WP+YzjSc6Skn3rtbMgL9zjWAJ/fqWxnMOeyiHSLfqHwi2D0AxR8rSTcHl13/l9GX6S0= X-Received: by 2002:a17:90a:d081:b0:25d:d224:9fb9 with SMTP id k1-20020a17090ad08100b0025dd2249fb9mr18445719pju.24.1687185043097; Mon, 19 Jun 2023 07:30:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sahil Harpal Date: Mon, 19 Jun 2023 19:59:58 +0530 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: Dave Page Cc: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="0000000000002a0e7205fe7c61ab" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002a0e7205fe7c61ab Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 the >> values are wildly different (which is likely). > > > So should I combine all the parameters (Total read/write operations, Tota= l > Bytes read/write, and time spent) in a single graph for one disk or just > the total number of read/write operations? > Could you please also clarify this? 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, Tota= l > 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 ea= ch >>> 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 w= rote: >>> >>>> >>>> >>>> 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 b= e >>>> 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 gro= uping >>>> 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 t= he >>>> 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 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 "Sy= stem >>>>>>> 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 ne= w >>>>>>>>> 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 wir= eframe 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 >> >> --0000000000002a0e7205fe7c61ab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=3D""
On = Fri, 16 Jun 2023 at 14:15, Sahil Harpal <sahilharpal1234@gmail.com> wrote:
3D"image.gif"
I think combining R/W is fine, as long a= s it uses two scales in case the values are wildly different (which is like= ly).

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?

Could you= please also clarify this?


On Fri, 16 Jun 2= 023 at 14:15, Sahil Harpal <sahilharpal1234@gmail.com> wrote:
I think combining R/W is fine, as long = as it uses two scales in case the values are wildly different (which is lik= ely).

So should I combine all the parameters (To= tal read/write operations, Total Bytes read/write, and time spent) in a sin= gle graph for one disk 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@e= nterprisedb.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 each parameter=C2=A0for all the disks?

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

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

<= /div>
O= n Thu, 15 Jun 2023 at 09:55, Sahil Harpal <sahilharpal1234@gmail.com> wrote:<= br>
Hi Aditya,

Thank you for pointing this= out. It would also be more convenient for users to navigate to specific st= atistics easily.

So, can we finalise the following design?
- Sing= le 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.
=C2=A0
- = Clubbing OS, CPU, Process, Disk and I/O in tabbed control.

I think the current design has too much o= n one big page, so yes, I'd want to see those split up onto different t= abs. Not sure about the grouping though. Maybe:

Su= mmary (OS info, system specs etc)
CPU
Memory
= Storage (including I/O)

Process info would be incl= uded on each tab as related to that tab's content - e.g. CPU per proces= s on the CPU tab, memory per process on the memory tab, etc..)
=

Thanks,
Sahil

<= /div>
3D""
= On Thu, 15 Jun 2023 at 11:21, Aditya Toshniwal <aditya.toshniwal@enterprised= b.com> wrote:
Hi Sahi= l,

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 ne= twork 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 <sahilharpal123= 4@gmail.com> wrote:
Thank you, Akshay, for yo= ur feedback.=C2=A0
Here are a few more designs that I have create= d based on the discussion with my mentors. I would love to know your though= ts=C2=A0on them.=C2=A0

Design 1 - Using an additional new= tab for system statistics
Design 2 - Added buttons to toggle between ex= isting dashboard data 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 "Genera= l"(Can be changed) and "System Statistics".=C2=A0=C2=A0

Thanks,
Sahil




<= img width=3D"0" height=3D"0" alt=3D"" style=3D"display: flex;" src=3D"data:= image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7">=
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 created a new tab System Statistics instead of using the ex= isting dashboard.=C2=A0

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 wireframe to display system = stats on the existing dashboard.

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

Than= ks,
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

--0000000000002a0e7205fe7c61ab--