If issue related with ABP Framework
- What is ABP Framework version? Zero 8.1 with .NET Core 3.1
Hi,
We're currently facing memory issues in our deployment now that a couple users work with it on a daily basis. Before that, the system being more or less in stand-by, it ran for weeks/months without issues, but now it ran out of memory two times in two days. We deployed to docker with 8 GB RAM in total, and it was the Zero Host container (dotnet) that consumed it. The strange thing is how suddenly the used amount jumps:
Shortly after that, the Debian host almost stalled due to swapping.
I searched through audit logs and host logs to find any suspicious user activity but found none.
Do you have an idea what causes that? Is there any background activity in Zero which could explain that?
Thanks in advance!
3 Answer(s)
-
0
Hi @ips-ad
Could you share your ABP NuGet package version ? Is it possible for you to upgrade APB NuGet packages to latest 6.x at least ?
-
0
Thanks for your fast reply! Those packages should be all on Zero's 8.1 standard version (we're planning to upgrade Zero in the future, but due to the amount of work to update all our entities, this won't happen in the next few months). Please find screenshots below. Honestly I don't feel good with upgrading a bunch of packages and thus leaving 8.1 standards - this involves complete testing of everything before releasing a new version. If you suspect a specific package, that's something else though.
What we did in the meantime and would like to hear your opinion on that, too:
- Update aspnet:3.1-buster-slim from 3.1.9 to 3.1.22 (Docker/Portainer doesn't that automatically when creating a new app image)
- Limit the container's memory to 5 GB (I read that such a limit should force .Net Core apps into some sort of garbage collection before the docker host stalls)
Thanks again for your support!
-
0
Hi @ips-ad
We made some performance improvements in 6.x and 7.x versions of ABP packages. Is it possible for you to upgrade to at least latest 6.x version of ABP and try again ? You also need to upgrade to .NET 5 I guess.
