HIGH_PERF_INDEXED=1;
does what it did before: enable high performance with power of 10 tables (1 / 10 / 100ms slot-base).
And now, new: an additional switch to change the table base from power of 10 to power of 2:
HIGH_PERF_BASE2=1;
You need BOTH switches together to compile the high performance index code for power of 2 tables (1 / 8 / 64ms slot-base).
The “…Fast” projects / options in Visual Studio 19 (HIGH_PERF_INDEXED=1;) are renamed to “…FastBase10” and keep working with high performance index tables on base 10.
The additional “…FastBase2” projects in Visual Studio 19 set both compile switches (HIGH_PERF_INDEXED=1; HIGH_PERF_BASE2=1;) and work with high performance index tables on base 2.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
see TCN-TRDP2-D-BOM-019-10 System Architecture & Design Spec
Last edit: Armin-Hagen Weiss 2021-10-06
Diff:
Now there are now 2 compile switches:
HIGH_PERF_INDEXED=1;
does what it did before: enable high performance with power of 10 tables (1 / 10 / 100ms slot-base).
And now, new: an additional switch to change the table base from power of 10 to power of 2:
HIGH_PERF_BASE2=1;
You need BOTH switches together to compile the high performance index code for power of 2 tables (1 / 8 / 64ms slot-base).
The “…Fast” projects / options in Visual Studio 19 (HIGH_PERF_INDEXED=1;) are renamed to “…FastBase10” and keep working with high performance index tables on base 10.
The additional “…FastBase2” projects in Visual Studio 19 set both compile switches (HIGH_PERF_INDEXED=1; HIGH_PERF_BASE2=1;) and work with high performance index tables on base 2.