but I am a bit afraid that the memory usage for example might change over time?
It will of course, but apart if you have some memory leak somewhere, it will tend to stabilize over time. Ah well - I will have to monitor this for an extended period of time and see what happens then :-) For sure. I can't see any other way to have a realistic assessment otherwise. Once you'll get some figures, you can elaborate the limits by adding a bit of headroom (let's say 20% more for instance). You can reduce this amount if you are short, or if you observe that the situation is rather stable, but in this case there's a risk for K8S to kill and restart your pods too often. In any case, it's a matter of compromises. Regards Eric ________________________________ From: django-users@googlegroups.com <django-users@googlegroups.com> on behalf of Andréas Kühne <andreas.ku...@hypercode.se> Sent: Tuesday, October 30, 2018 1:25:11 PM To: django-users@googlegroups.com Subject: Re: Using django on kubernetes Thanks for the replys, I am of course monitoring the resources - but I am a bit afraid that the memory usage for example might change over time? Ah well - I will have to monitor this for an extended period of time and see what happens then :-) Regards, Andréas Den tis 30 okt. 2018 kl 12:17 skrev Jason <jjohns98...@gmail.com<mailto:jjohns98...@gmail.com>>: using infrastructure monitoring such as new relic can lend valuable insight into what resources pods are using vs their default allocation -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com<mailto:django-users+unsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com<mailto:django-users@googlegroups.com>. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7972f667-e1a6-4115-b75c-2e8656e256c3%40googlegroups.com<https://groups.google.com/d/msgid/django-users/7972f667-e1a6-4115-b75c-2e8656e256c3%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com<mailto:django-users+unsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com<mailto:django-users@googlegroups.com>. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAK4qSCcwq8ca6VDO0coxQjES9%2BOjEyt%2BKSQmJD5e231gocvRgA%40mail.gmail.com<https://groups.google.com/d/msgid/django-users/CAK4qSCcwq8ca6VDO0coxQjES9%2BOjEyt%2BKSQmJD5e231gocvRgA%40mail.gmail.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/VI1P193MB04326CEE8E9089F61D7CE3B78CCC0%40VI1P193MB0432.EURP193.PROD.OUTLOOK.COM. For more options, visit https://groups.google.com/d/optout.
