When we submit a series of GET-requests to the SageCRM Rest API, the first request takes up a great amount of time: at least 500 ms. Using the SQL Server Profiler I discovered that (at the first GET-request) there are two SQL Select statements executed to get user data (with column 'User_Logon', taken from basic authentication). Between the first and second SQL Select script the profiler shows just over 400 ms. This only occurs at first GET request.
To get the actual data as a response for the first GET-request three subsequent SQL Select statements are executed: again to get user data, then a 'SELECT COUNT(*) FROM ...' on the entity requested, followed by a 'SELECT TOP 10 ...' on the entity requested (10: default count). This takes only a couple of ms.

Question:
What happens in Java code when the session is created? Why does setting up the session take such a relatively long time?
And... is there a way to change logging levels to get some insight on the creation of sessions?

Our Sage configuration:
Application and SQL Server database are on the same server. There is very much free disk space. In Sage are only one company and one person with one email address. All requests are made from the application server. There is some hardening in effect.