2 ms·
I assume your docker taking GBs above is for Windows Containers? Also, most of that overhead is first use, updates and parallel similar containers are much sma
by tracker1 8y ago
I assume your docker taking GBs above is for Windows Containers? Also, most of that overhead is first use, updates and parallel similar containers are much smaller. Also, as you mention, alpine containers are what I'd consider "just enough" when wanting to diagnose an app in a container.
I've found that .Net Core on Linux and in Windows are close enough that scaling should be the bigger concern. Unless you're tethered to windows, the broader tooling is much more mature with Linux containers/pods.
- chupasaurus 8y ago.Net has some caveats with GC: Server GC preallocates heap per CPU core so if you have 8+ server it could be a waste of RAM if app uses less than 1GiB. We are tinkering with microservices on .Net Core 2 in k8s and came up with using WS mode with clearing unused allocated memory on health check calls which is dirty but working trick. On the Java side though there is a hack in JRE which checks if JVM runs inside a Docker container in order to not get out of memory limit by cgroup.
- GordonS 8y agoI believe the are changes coming in .NET Core 3.0 to fix the OOTB server-GC situation. Of course for now you always have the option of enabling desktop GC instead