There is a remarkable amount of memory allocation occurring under load to perform the "app." prefixing of field names by the Beeline.
Short description of the changes
This change skips the memory allocations needed for string concat and usage if the "app." prefix is already present on the field name provided.
Benchmarks
Existing behavior is no slower or memory hungry, but for every field name provided by the Beeline user that starts with "app.", that is one less memory allocation of the size of the field name string.
Which problem is this PR solving?
There is a remarkable amount of memory allocation occurring under load to perform the "app." prefixing of field names by the Beeline.
Short description of the changes
This change skips the memory allocations needed for string concat and usage if the "app." prefix is already present on the field name provided.
Benchmarks
Existing behavior is no slower or memory hungry, but for every field name provided by the Beeline user that starts with "app.", that is one less memory allocation of the size of the field name string.