My thinking was to try at build time to have some automated performance testing.
Not necessarily for every build but maybe leading up to the final or RC (maybe even as part of "NETCAT" type of testing), it would be run and then performance metrics / benchmarks would be published someplace (I suppose maybe as a jenkins result/report, but not sure if over time that is the best place to store it) which can be reviewed/compared over time to see where performance bottlenecks (are and maybe placed for improvement) or performance degradation may have started showing up (i.e. some new changes adds excessive performance hits and may need to be reworked to be more efficient or have to accept the hit). Eric Bresie [email protected] On Sun, Feb 21, 2021 at 5:36 PM Kirk Pepperdine <[email protected]> wrote: > Hi Eric, > > Can you provide more details as to what you’re trying to do and what you > are expecting to see? > > Kind regards, > Kirk > > > > On Feb 20, 2021, at 11:25 AM, Eric Bresie <[email protected]> wrote: > > > > Other than running performance within Netbeans, is there a way for the > > Netbeans code base test suites to be used to run and generate performance > > metric reports based on the testing. The results can be published in > some > > form of build report and identify possible performance bottlenecks in the > > code and/or run periodically (maybe as part of "pre-release" testing) to > > see when changes have impacted performance significantly.. > > > > Eric Bresie > > [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
