From: | Shirley Wang <swang(at)pivotal(dot)io> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | [Design Update][Dashboard] |
Date: | 2017-03-02 17:10:55 |
Message-ID: | CAPG3WN6RH6qOXmunu7x=DCjC8O9Hf9v-BE_w+Zy2G5hddedNcA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hello Hackers,
Below is an update on our findings for the Dashboard in pgAdmin. You can
also find all updates here:
https://docs.google.com/document/d/1J_GhsL0nR4dbTI6F-XlxspvXutghzj-3UGjDWf8MtVA/edit?usp=sharing
. . .
*Summary*
We wanted to learn if the graphs within the ‘Dashboard’ option had
relevance for Greenplum users (Greenplum has a product, Command Center,
which supplies DBAs with similar information).
*Database Sessions*
-
Users know it’s for understanding how many active and idle sessions
there are
-
Most useful for DBAs
*Transactions per Second*
-
Not useful for users, only DBAs
-
Users felt like a longer time frame would be more useful, like per hour
or 30 min
*Block I/O*
-
Information that is found in Command Center
-
Provides useful feedback for DBAs on how to improve the system
*Tuples* In
-
Used as a way to determine what actions to take given what kinds of
queries are going on in the system
-
Would be more useful if could see table information (which tables are
being calculated)
-
Part of Command Center
*Tuples Out*
-
Not particularly useful for users
-
Distinction between metrics is difficult to remember
*Actions*
-
Share these learnings with GPCC team
-
Remove these graphs for users who are connected to a Greenplum database
-
Information provided is useful for DBAs who are using a Postgres
Database and should remain for those users
From | Date | Subject | |
---|---|---|---|
Next Message | Atira Odhner | 2017-03-02 18:11:55 | [discussion] Javascript package management (Yarn?) |
Previous Message | Shirley Wang | 2017-03-02 17:08:30 | [Design Update][Autoformat] |