First, xdebug should not be enabled when you are running benchmarks; it has known, severe impact on performance.
Second, we really need to know what you are benchmarking: is it a default skeleton? Are templates involved or not? which container was used? are you hitting the home page, a 404, an error page, or…? These sorts of details allow us to attempt to recreate the benchmark. Ideally, we should have a comparable setup in the other framework against which you are benchmarking, so we can iron out any other factors (e.g., is there any cache priming happening).