As the Addresscomponent is configured to be lazily loaded more SQL queries are run to fetch the required data i.e. first the Person and then his Address.
This could have been avoided by loading both the Person and the Addresscomponent in a single query because we knew that our business use case required both components.