On 03/17/2014 01:03 PM, Francesco Romani wrote:
----- Original Message -----
From: "Francesco Romani" <[email protected]>
To: "Antoni Segura Puimedon" <[email protected]>
Cc: "vdsm-devel" <[email protected]>
Sent: Monday, March 17, 2014 10:32:40 AM
Subject: Re: [vdsm] Profiling and benchmarking VDSM
next immediate steps will be
- have a summary page to collect all performance/profiling/benchmarking page
Links added at the bottom of the VDSM developer page:
http://www.ovirt.org/Vdsm_Developers
see item #15
http://www.ovirt.org/Vdsm_Developers#Performance_and_scalability
- document and detail the scenarios the way you described (which I like)
the benchmark templates will be attached/documented on this page
Started to sketch our "Monday Morning" test scenario here
http://www.ovirt.org/VDSM_benchmarks
(yes, looks quite ugly, no attached template yet. Will add).
I'll wait a few hours to let things cool down a bit and see if something
is missing, then start with the benchmarks using the new, proper definitions
and a more structured approach like the one documented on the wiki.
http://gerrit.ovirt.org/#/c/25678/ is the first in queue.
can we add the profiling decorator on each nose test function and share
results link with each push to gerrit?
the issue is that it collects profiling only for one function in a file.
we need somehow to integrate all outputs..
the nose tests might be good to check the profiling status. it should
cover most of the flows specifically (especially if we'll enforce adding
unit tests for each new change)
--
Yaniv Bronhaim.
_______________________________________________
vdsm-devel mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
