Re: [GSoC] Summery of pg performance farm

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Hongyuan Ma <mahongyuan1997(at)gmail(dot)com>
Cc: Mark Wong <mark(at)2ndquadrant(dot)com>, sfrost(at)snowman(dot)net, pgsql-hackers(at)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [GSoC] Summery of pg performance farm
Date: 2018-08-19 15:20:37
Message-ID: 20180819152037.klyhkrsyiwoowh45@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-Aug-19, Hongyuan Ma wrote:

> Hello monters and hackers,

Is that "monsters" or "mentors"?

> 2. Implementation of the data report related to the list page. Compare each
> metrics whith the previous results. If any of the metrics are a 5%
> improvement( or regression), there is one aspect that is progressive (or
> regressive). This means there may be aspects of "improvement", "regression"
> and "status quo" in one test result.This is the report List page for an
> example: http://140.211.168.111/#/machineInfo/pmJEjJjSk3WREM3Q

Great stuff!

I think the visualization that many had in mind was that the numbers
would be displayed in charts there time is the horizontal axis, and the
numerical performance result number is the other axis. That way, we
can see how the results go up or down with commits.

Individual happy/sad faces for individual commits are not enough to see
the bigger picture.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2018-08-19 17:29:15 Re: Fix for REFRESH MATERIALIZED VIEW ownership error message
Previous Message Hongyuan Ma 2018-08-19 07:53:55 [GSoC] Summery of pg performance farm