EDIT

using jackson instead of json-lib may have an significant impact on the REST service performance:

perfomance of json-lib by comparig two REST service calls:

1. generic service: ab -n 20 'http://127.0.0.1:8080/description/distributionInfoFor/0eb6ca37-3365-4af5-a800-8fc4b8c366fa.json?statusOrderPreference=1&subAreaPreference=1&hideMarkedAreas=70ceb5bc-3413-4b4e-8ef3-de29d06a42a5&part=mapUriParams&part=tree&part=elements'

• 31kb / response

• Max time: 1,991s

• Min time: 0.766s

• Average: 0,854s

1. portal service: ab -n 20 'http://127.0.0.1:8080/portal/description/distributionInfoFor/0eb6ca37-3365-4af5-a800-8fc4b8c366fa.json?statusOrderPreference=1&subAreaPreference=1&hideMarkedAreas=70ceb5bc-3413-4b4e-8ef3-de29d06a42a5&part=mapUriParams&part=tree&part=elements'

• 500kb /response

• Max time: 3,689s

• Min time: 1,133s

• Average: 1,325s

It looks like the amount of objects to be serialized is consuming an significant amount of time.

further incidence is given by the following benchmark results:

• http://www.cowtowncoder.com/blog/archives/2009/02/entry_213.html

• http://www.cowtowncoder.com/perf/json-count-2009-02-20-2cpus/index.html

For further evidence see [#4925#note-7]

additional TODO once this is done perform the measurements taken for #4925

for spring configuration see: https://docs.spring.io/spring-boot/docs/current/reference/html/howto.html#howto.spring-mvc.customize-jackson-objectmapper

Related tickets:

• Duplicate #3440