You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that after I either use Hash() or Verify() functions, memory drastically increases but is not released. My service will go from around 150MB to 600 MB+ which is what is supposed to happen, right? Since that is point of Argon2, to be memory heavy, right? But memory is not released and service is just running with 600+ MB from now on.
I tried to explicitly call GC.Collect() after Argon2 functions, and it releases some because then memory usage is around 450 MB which is better but still not good. I also tried to explicitly dispose my DbContext which also drops memory usage for about 100 MB more but I don't understand why that is even happening. If I turn off all Argon2 functions (comment all Argon2 code), service runs with around 150MB and DbContext has not effecting it ever.
I suspect there is some issues with garbage collection with Argon2.
The text was updated successfully, but these errors were encountered:
I noticed that after I either use
Hash()
orVerify()
functions, memory drastically increases but is not released. My service will go from around 150MB to 600 MB+ which is what is supposed to happen, right? Since that is point of Argon2, to be memory heavy, right? But memory is not released and service is just running with 600+ MB from now on.I tried to explicitly call
GC.Collect()
after Argon2 functions, and it releases some because then memory usage is around 450 MB which is better but still not good. I also tried to explicitly dispose my DbContext which also drops memory usage for about 100 MB more but I don't understand why that is even happening. If I turn off all Argon2 functions (comment all Argon2 code), service runs with around 150MB and DbContext has not effecting it ever.I suspect there is some issues with garbage collection with Argon2.
The text was updated successfully, but these errors were encountered: