The expressions defining properties are evaluated for each benchmark independently

This allowed me to use the benchmark.activeSize and benchmark.maxSize variables, set to correct number for each benchmark size.
The motivation was to have the same load (number of threads)  when increasing the cluster size - I had to set numThreads="#{ 40 benchmark.activeSize / }"