VBart Wrote: > It most likely that your system memory allocator do not return freed > memory to the OS. How can I check this? I suspect this should be part of the OS (Linux)? Could you give me any keyword to read more about this? I looked at /proc/meminfo after the first and second batch of requests. The newly allocated memory is categorized as "Active(anon)": > Acby peschuster - Nginx Mailing List - English
I don't use any third-party modules, neigther SSL or gzip. nginx was compiled using the following parameters: > --with-debug \ > --without-http_rewrite_module \ > --without-http_gzip_module nginx only serves one static file. Changing the size of the file (10 KB to 200 B) has no effect on the memory comsumption of nginx. Here is my nginx.conf: > user nobody; > workerby peschuster - Nginx Mailing List - English
Hi, I cross-compiled nginx for microblaze processors (http://github.com/peschuster/nginx) and am currently doing some performance benchmarks with nginx running on a microblaze processor with a custom designed SoC on a FPGA. However, I am having problems with the memory consumption of nginx: When I perform 10,000 requests with 20 conn/s and 2 requests/conn (using httperf - 1), memory usedby peschuster - Nginx Mailing List - English