Audit the need of the data being queried for session response

[rathorevaibhav]

Describe the task
We're querying several tables when sending a session response. These queries must be running for both session create and update requests. The latter is called every 10sec on the Player page, which might lead to unnecessary load on the DB server.

I still need to verify but this might be the reason for the backend failing to respond when under a huge amount of load from K6.

Expected behavior

• Propose a solution that can help with reducing the redundant queries or a faster performance (caching?)
• See if there's a way (like GraphQL) where the query response data can be controlled by the requestor.

[rathorevaibhav]

Results from Silk query profiler

Session Create request (local):

Session Update request (local):

These are definitely ultra-expensive queries.