Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Controlled active CMA-ES implementation diagnostic

These are paired wall-deadline measurements of fcmaes-core and cmaes 0.2.2. Both use active (negative-weight) CMA-ES, the same normalized reflected objective, explicit population size, initial mean, and sigma. This is an implementation diagnostic, not a general CMA-ES performance benchmark: its easy analytic functions isolate overhead, scaling, and stopping behavior rather than recommending CMA-ES for those functions. Matching numeric seeds label pairs but do not create matching random streams. A run may exceed its deadline by one generation.

Bundle summary

Raw rowsComplete pairsObjective callsActive wallProcess CPU
14472105934400.001 h0.011 h
LibraryInternal-stop rowsAll rows
fcmaes-core072
cmaes2172

Paired final-objective outcomes at the longest endpoint (50 ms):

Armfcmaes-core winscmaes winsTiesPairs
a25512
b13812
c51612

Detailed results

The table reports medians over available seeds. Wins compare final objective values within a relative 1e-10 tie band. Residual ns/eval is shown only for serial Arm A and subtracts the separately measured shared-objective calibration; it is diagnostic, not a library-internal profiler.

ProblemCostArmDeadlinePairsWins fc/cma/tieInternal stops fc/cmaMedian best fcMedian best cmaMedian eval/s fcMedian eval/s cmaAllocated cores fcAllocated cores cmaResidual ns/eval fcResidual ns/eval cma
rosenbrock100 nsa10 ms30/0/30/34.654279e-281.226575e-23150573520449161.000.37597422
rosenbrock100 nsa50 ms30/1/20/34.520173e-281.496247e-23158401820268711.000.08564426
rosenbrock100 nsb10 ms30/3/00/02.176932e-19.444679e-338430142260314.5513.87——
rosenbrock100 nsb50 ms30/1/20/35.324811e-281.496247e-2342475647252014.524.80——
rosenbrock100 nsc10 ms30/0/30/34.007413e-285.335656e-24164637221273737515.9712.62——
rosenbrock100 nsc50 ms30/0/30/31.751271e-286.254638e-24164778951104498615.992.51——
rosenbrock10100000 nsa10 ms32/1/00/01.759929e31.174851e3992999401.001.00675563
rosenbrock10100000 nsa50 ms31/2/00/01.196717e19.939553e0993499511.001.00618446
rosenbrock10100000 nsb10 ms32/1/00/08.338046e09.440543e0775968052911.1910.79——
rosenbrock10100000 nsb50 ms31/2/00/05.632147e-21.890527e-2783087762811.1711.13——
rosenbrock10100000 nsc10 ms30/3/00/04.367944e23.516178e214787615365414.9115.49——
rosenbrock10100000 nsc50 ms32/1/00/08.189657e08.709281e015803815828915.9715.97——
sphere100 nsa10 ms30/0/30/00.000000e00.000000e0147215120358801.001.00615427
sphere100 nsa50 ms30/0/30/30.000000e00.000000e0150350621653851.000.44601398
sphere100 nsb10 ms30/0/30/02.376049e-270.000000e039961259607512.9313.35——
sphere100 nsb50 ms30/0/30/00.000000e00.000000e051586654982514.3514.03——
sphere100 nsc10 ms30/0/30/00.000000e00.000000e0154895061707973415.9515.80——
sphere100 nsc50 ms30/0/30/30.000000e00.000000e0155656381501605115.9812.85——
sphere10100000 nsa10 ms31/2/00/04.246298e06.302844e0991899431.001.00780520
sphere10100000 nsa50 ms31/2/00/01.377269e-21.352301e-2993599511.001.00607439
sphere10100000 nsb10 ms32/1/00/02.280751e-41.819043e-4764168178911.1910.85——
sphere10100000 nsb50 ms30/0/30/05.745432e-262.077860e-26787048212711.1010.95——
sphere10100000 nsc10 ms31/2/00/02.391887e03.663828e015366614821015.5014.94——
sphere10100000 nsc50 ms33/0/00/01.868115e-32.704991e-315780715803915.9515.94——

Interpretation boundary

The three arms isolate different implementation choices:

  • Arm A is the closest same-family implementation comparison.
  • Arm B also compares each library’s population-evaluation path.
  • Arm C gives both implementations the same independent-multistart architecture.

None of these rows compares fcmaes coordinated DE→CMA retry with cmaes BIPOP. That is a different-algorithm system comparison covered by the broader optimizer benchmark.

The analytic controls do not show that CMA-ES is the right solver for them. For sufficiently costly application objectives, the measured implementation overhead also becomes irrelevant. Smoke and pilot presets validate the harness; they are not publication evidence.