What exactly do you mean by building the model "interactively"?
And what exactly are the performance issues you observe?
The overhead for Concert is mainly for building the model (also known as "extraction"). Once the solve has started, the executed code should be the same for callable library and Concert. An exception is using callbacks. For every callback invocation Concert has to go back and forth between the native C code in the engine and Java.
#CPLEXOptimizers#DecisionOptimization