You looked in |massif.out.<pid>|, for the output, I hope. If that does
not help, there is info that suggests you might need
|--pages-as-heap=yes|
http://valgrind.org/docs/manual/ms-manual.html#ms-manual.not-measured
Nginx has child processes, as you will have seen here:
https://www.nginx.com/blog/inside-nginx-how-we-designed-for-performance-scale/
So I am guessing you might need to tell valgrind (this is from the man
page):
--trace-children=no|yes Valgrind-ise child processes (follow execve)? [no]
On 2016-10-03 05:01 AM, Muhui Jiang wrote:
Hi
I hope this this the right mailing list for technical support.
Recently, I tried to use Valgrind to analysis the popular server. I
use the tool massif in valgrind to try to analysis the heap allocation
inside Nginx. I use the command
valgrind --tool=massif /path/to/nginx
to start the massif. I noticed that massif will only profile the
memory information for starting up nginx. I want massif to profile the
related heap information when I make request to the servers. Does
anyone have any ideas or comments on this? Many Thanks
Regards
Muhui
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
