Il 14/04/2016 14:50, Daniel Nicoletti ha scritto:
2016-04-14 9:26 GMT-03:00 Javier Guerra Giraldez <[email protected]>:
On 14 April 2016 at 13:22, Daniel Nicoletti <[email protected]> wrote:
It's not unfair since threads are basically process to linux kernel
in the Linux kernel threads and processes are indeed different kinds
of a generic task concept; the main difference being that each process
has its own memory space and a thread does not.
therefore, while they might be comparable in some aspects, definitely
not in memory consumption.
Sure, but assuming you don't have requested memory they should be pretty
close on the memory usage.
And yes, I just did another test creating a list allocating a good
ammount for each
worker process before forking and the result is that I can now I get to what
happens in uwsgi.
What you are describing is what you should expect after fork.
So it's quite possible that uwsgi could reduce this.
Let me say it again, if you want to help with that fire up valgrind and see
where the memory is used and eventually leaked.
--
Riccardo Magliocchetti
@rmistaken
http://menodizero.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
