>Stephen Frost <sfr...@snowman.net> wrote: > The goal is to have this running in a similar manner as the build > farm to identify when a patch has an impact on performance (good > or bad). Hackers would then be able to view performance farm > reports similar to viewing build farm reports. Not sure if we'd > have alerts or something, but I'd think in alot of cases a given > hacker would know that they're commiting something performance- > impacting (or saw someone else commit something that could be) and > they'd go check out the performance farm reports a few days later > to determine if there was a change. I actually understood that part, but was already wondering if it could be bent to slightly different purposes. It seems as though there would be value to using it to evaluate the performance impact of a proposed patch, at least on a limited basis, *before* a commit. If there's not an immediately obvious way to put it to that alternative use, that's OK; I just thought I'd ask. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
