The initial suspicion was that the bbox queries and reading the surface data from the csv files is too slow. However, much much more time is spent on other things than on the functions that get the data for the response.
See https://github.com/3DGI/3dbag-api#performance and #14 (comment) and #15 (comment).
Thus these functions are by far not the bottlenecks in the response times, but what is?
The profiler statistics in /profiling is a good starting point.
The initial suspicion was that the bbox queries and reading the surface data from the csv files is too slow. However, much much more time is spent on other things than on the functions that get the data for the response.
See https://github.com/3DGI/3dbag-api#performance and #14 (comment) and #15 (comment).
Thus these functions are by far not the bottlenecks in the response times, but what is?
The profiler statistics in /profiling is a good starting point.