Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qXJYI-005xXW-BP for pgadmin-hackers@arkaria.postgresql.org; Sat, 19 Aug 2023 10:51:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qXJYG-00GgDV-Rc for pgadmin-hackers@arkaria.postgresql.org; Sat, 19 Aug 2023 10:51:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qXJYG-00GgDM-Jn for pgadmin-hackers@lists.postgresql.org; Sat, 19 Aug 2023 10:51:28 +0000 Received: from mail-pg1-x52e.google.com ([2607:f8b0:4864:20::52e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qXJYD-000y1p-Jw for pgadmin-hackers@postgresql.org; Sat, 19 Aug 2023 10:51:27 +0000 Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-565dc391be3so2010816a12.0 for ; Sat, 19 Aug 2023 03:51:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692442284; x=1693047084; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Wd7/VJ4QKDX30/H7JbNkV14XAo7G/EHhH4hhn9LxrDA=; b=aNfU5vwzIjM90Y87Tv9dAxNBuG2xTYwcc4mYsINhuEqc68cTcc+njIOkaVUP0V01nE vKBxXsdnRXWjDZfuE0lEYBqJBPnW0S0NzX4pzx+tbB4YjD0mvs6Dw/faTevEcs1pwBb8 S5Xp/1tiGcWCsHpuDg1ZqS3Mw7kpFgj6k3Pk/Q48SrAN5k6cW57YLo9EJTzVd2eqnKq2 KfB4M7vPUrkyCK3tqQNNwWnNpYupc0eTLrEVa2YsN10B29I43OHymVg5tZaWNQEYaYI/ vwNXvEUhOZ+Xa57szFi8wY1O1SJWnmWNA0Ye5sksW/adeDyafa1O/F2OHsx5zLnyDUUO 9HxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692442284; x=1693047084; 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=Wd7/VJ4QKDX30/H7JbNkV14XAo7G/EHhH4hhn9LxrDA=; b=GB+nEje6X6SSHiOXCJNhBhvNd+ypfcJAkUXbB+WAAtdfLVHrTEKEnQmakJyKA8Njat sjfmGZ7XRVk2kGcO+c2KNSAJ1Pa/rOhC5IFsyHeRvkcd/5rWmzTLg6+32G1GMbf3PEjk KQ+k7/xEaLdDsS5aQYC/RLmxtxf7bvu1z2qn6x/8bXjIrq395TwgEdrRYdOZz+/s7P/6 4GCTZLKXAtEHu+fGBwV736lh+N4GzSPetL212b7yga+zOnDtSnEV+onYy5ePqVrHtlWc IQmLtjfn1w+3bFiigMWTTPeaLMTcNa7+835tpHTJQw/OCgf8K+wah/4r9JTVnYIZIyff 5vZA== X-Gm-Message-State: AOJu0YwgwjcPWSfpukKVPU7mgdlAMq2wK6CNE0VgVu5BBfy19thfMsTs 5o5VIbxiiQ56xmA0Vyi2DqxR9uEQmOzjLmP4FHjgSvcfPqF36Q== X-Google-Smtp-Source: AGHT+IEk+9+MHFsYSyVl9gI0hBbCb8VycwrPcYvk6DfF0sENezE3XkJV6d3m8FI1oickZzAmGgeRP1hKev9godbI0Yg= X-Received: by 2002:a17:90a:e393:b0:26b:d1c:7198 with SMTP id b19-20020a17090ae39300b0026b0d1c7198mr2435689pjz.8.1692442284144; Sat, 19 Aug 2023 03:51:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sahil Harpal Date: Sat, 19 Aug 2023 16:21:13 +0530 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: pgadmin-hackers@postgresql.org Cc: Khushboo Vashi , Dave Page , Aditya Toshniwal , Akshay Joshi , Ashesh Vashi Content-Type: multipart/alternative; boundary="000000000000263e7b0603446de3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000263e7b0603446de3 Content-Type: text/plain; charset="UTF-8" On Thu, 10 Aug 2023 at 00:37, Sahil Harpal wrote: > Pending Work: > > 1. Process information - > - Issue: The pg_sys_process_info() query takes much longer (more > than 2 mins) to execute and prevents the updation of other graphs and > tables. > 2. Disk information - > - Issue: The pg_sys_disk_info() query returns NULL value for some > of the drive letters. > 3. StreamingChart - > - Issue: Graph shifting glitch. For the first time, graphs start > from the opposite side, and after the following API call or a few seconds > later, those get adjusted. > > I need suggestions for labels for different tables and charts. Also, could > you please clarify the use of the counterData variable, which is used for > some of the charts (tps_stats, ti_stats, to_stats, and bio_stats)? > Could you please help me with these blockers and doubts? Thank you, Sahil --000000000000263e7b0603446de3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=3D""
On= Thu, 10 Aug 2023 at 00:37, Sahil Harpal <sahilharpal1234@gmail.com> wrote:
Pending Work:
  1. Process information -
    • Issue:= The pg_sys_process_info() query takes much longer (more than 2 mins) to ex= ecute and prevents the updation of other graphs and tables.=C2=A0
    =
  2. Disk information -
    • Issue: The=C2=A0pg_sys_disk_info() query= returns NULL value for some of the drive letters.
  3. StreamingCh= art -=C2=A0
    • Issue: Graph shifting=C2=A0glitch.=C2=A0For the first time, graphs start= from the opposite side, and after the following API call or a few seconds = later, those get adjusted.
I need suggestions for labels= for different tables and charts. Also, could you please clarify the use of= the counterData variable, which is used for some of the charts (tps_stats,= ti_stats, to_stats, and bio_stats)?
Could you please help me with these blockers and=C2=A0doubts?

Thank you,
Sahil
--000000000000263e7b0603446de3--