After benchmarking my interface application (built with http api) I encountered the problem with concurrency. A single call will be answered in about 100 ms and has a size of 5 kb. If a second consumer requests the Service at the same time the response time will be more than tripled (between 300-500 ms). The returned data is buffered in memory why there isn’t any other access to a database etc.
Do you have any serialized procedures inside the return mechanism that could be
optimized? ATM I can’t provide a stable performant service.