[no description] https://git.osdyson.ru/pkg-puppet/puppet/atom?h=master 2014-10-13T23:22:30Z 2014-10-13T23:22:30Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-10-13T23:22:30Z urn:sha1:ca6698f7aeeebab48f6e199c0cfa82d64b3dcc7c This makes the catalog_memory benchmark print a message about 2.1.0 being required and then exit with -1 unless the ruby version is >= than 2.1.0. 2014-10-13T20:18:42Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-10-12T23:19:52Z urn:sha1:d2ac0ae74d3bb7763d8f5e1f72d4d02af167fdc0 This adds a command that processes the dumped heap information produced by "catalog_memory" benchmark (or other similar heap-dumps). The result is a .dot file that can be rendered. This tool is useful when tracking a memory leak. 2014-08-05T23:24:31Z Josh Partlow joshua.partlow@puppetlabs.com 2014-08-05T23:24:31Z urn:sha1:189bcf577b2d74b15befdf3eb14a502ef888dbd3 2014-06-17T23:36:19Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-06-17T23:36:19Z urn:sha1:2ad30be7bccb351a86df10be29eb5805cefb0e4d This makes it possible for a benchmark scenario that wants additional details to run a smaller portion of the benchmark to configure these by defining a class called BenchmarkerTask (currently only used by the evaluations benchmark). The separation from the Benchmarker class is that this class is loaded when rake generates a list of tasks, and it is not wanted to load each full benchmark in turn to generate this list. (Over time, the BenchmarkerTask can be expanded on to perform other task generation duties). It is now possible to run all of the evaluations benchmarks, profile all, run one particular micro benchmark, or just its parse or evaluation part by suffixing the name with _parse or _eval. As an example rake benchmark:evaluations:run[assert_type_eval] runs only the evaluation part of the assert_type micro benchmark in evaluations. (This is especially useful when running profiling. For profiling, the parameter warm_up_runs is always included. 2014-06-17T21:02:11Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-06-16T19:27:43Z urn:sha1:e7447998b0e37ed24f689264bd3fbddfccb03e52 Arguments are needed to be able to run one detail of a benchmark. The evaluations benchmark makes use of this, all others ignore the arguments. 2014-06-17T21:01:48Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-06-13T22:08:29Z urn:sha1:8f78021df54fe0cb2331ed71b497670e760f69e8 This adds a benchmark that runs a series of puppet manifests that are measured individually for parse and evaluation time. Each manifest is measured 100x each for parse and evaluation. The benchmark total time includes running all of them (including overhead of measuring the details). Details are output as average of all runs per detail where parsing and evaluating is output as separate entries. The sample file written is for the total average. 2014-05-01T22:40:27Z Matthaus Owens matthaus@puppetlabs.com 2014-05-01T22:40:27Z urn:sha1:efbc32cef9c7c52874d5d50dbeeff0532d07de69 As this is an error/warning, the output should be put to STDERR instead of STDOUT so it can be easily filtered. 2014-04-18T05:03:19Z Kylo Ginsberg kylo@puppetlabs.com 2014-04-18T05:03:19Z urn:sha1:d6749c737ceace27aa69048ee87f12052fc1f103 2014-03-07T22:05:43Z Peter Huene peter.huene@puppetlabs.com 2014-03-07T22:05:43Z urn:sha1:7c4cfe23ec8b57c732b28a99701ca8fdda899c67 If rspec isn't installed, rake will fail because the parallel.rake file cannot be loaded. The fix is to only define the task if rspec/facter can be loaded. 2014-03-07T18:19:09Z Peter Huene peter.huene@puppetlabs.com 2014-03-06T21:55:57Z urn:sha1:420a9db6600405fb40a85e5279a36456779a3887 Adding a 'parallel:spec' task that will group specs and then run those groups in a parallel set of processes. By default, parallel:spec will bunch the specs into groups of approximately 1000 and concurrently run each group up to the number of processors reported by facter. The task takes two parameters: process_count and group_size. Running with a process_count of 1 (parallel:spec[1]) will behave like the existing 'spec' task, except it will still group the tests and recycle the spec running process between groups. This has the added benefit of limiting the spec running process' working set, at the cost of being a little slower.