| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Recording test runtimes with the buildfarm |
| Date: | 2020-06-11 21:44:32 |
| Message-ID: | 552015.1591911872@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On 6/11/20 12:32 PM, Tom Lane wrote:
>> Yeah, I don't see why we can't scrape this data from the existing
>> buildfarm output, at least for the core regression tests. New
>> infrastructure could make it easier/cheaper, but I don't think we
>> should invest in that until we've got a provably useful tool.
> OK, that makes my life fairly easy. Are you wanting this to be
> automated, or just left as an exercise for researchers for now?
I'm envisioning the latter --- I think somebody should prove that
useful results can be obtained before we spend any effort on making it
easier to gather the input numbers. Mind you, I'm not saying that
I don't believe it's possible to get good results. But building
infrastructure in advance of a solid use-case is a recipe for
building the wrong thing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2020-06-11 22:03:33 | Re: [PATCH] fix two shadow vars (src/backend/commands/sequence.c) |
| Previous Message | Melanie Plageman | 2020-06-11 21:29:15 | Re: Find query characters in respect of optimizer for develop purpose |