[Performance] GET /api-chat/rooms

[ghkdqhrbals]

GET /api-chat/rooms

• Implements
  • To solve JPA N+1 problems, EAGER fetching!
• Resource consumption
  • chat-db : 0.23 cpu
  • chat-server : 0.69 cpu
• Improvements
  • avg MTTFB : 406.65 -> ...
  • avg TPS : 247.6-> ...

Hibernate: select f1_0.friend_seq,f1_0.friend_id,f1_0.user_id from friend f1_0 where f1_0.user_id=?                                                                                                       
Hibernate: select u1_0.user_id,u1_0.user_name,u1_0.user_status from user_chat_table u1_0 where u1_0.user_id=?                                                                                             
Hibernate: select u1_0.user_id,u1_0.user_name,u1_0.user_status from user_chat_table u1_0 where u1_0.user_id=?                                                                                             
Hibernate: select u1_0.user_id,u1_0.user_name,u1_0.user_status from user_chat_table u1_0 where u1_0.user_id=?                                                                                             
Hibernate: select u1_0.user_id,u1_0.user_name,u1_0.user_status from user_chat_table u1_0 where u1_0.user_id=?                                                                                             
Hibernate: select u1_0.user_id,u1_0.user_name,u1_0.user_status from user_chat_table u1_0 where u1_0.user_id=?
// This select query coninue until all user were found //

[ghkdqhrbals]