You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@james.apache.org by "chibenwa (via GitHub)" <gi...@apache.org> on 2023/06/02 10:10:27 UTC

[GitHub] [james-project] chibenwa commented on pull request #1579: [FIX] JPA blocking calls should be moved to bounded elastic

chibenwa commented on PR #1579:
URL: https://github.com/apache/james-project/pull/1579#issuecomment-1573487316

   So I tracked down and detected the leak:
   
   Spawn a dockerized JPA james locally thanks to docker and imapsync my company emails to it...
   
   ### Before
   
   ![Screenshot from 2023-06-02 10-04-33](https://github.com/apache/james-project/assets/6928740/76596807-b9cf-48d6-b207-9143df97f8b6)
   
   GC is unable to reclaim memory, showing a leak that eventually builds up to an OOM.
   
   ## After
   
   ![Screenshot from 2023-06-02 17-09-47](https://github.com/apache/james-project/assets/6928740/dac3f17b-2cc4-4d9c-940d-c6684bbef1b8)
   
   
   We are waaaay better at reclaiming the damn memory.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org