On Fri, 2018-11-23 at 08:15 -0700, Gary Gregory wrote: > On Fri, Nov 23, 2018 at 2:27 AM Oleg Kalnichevski <[email protected]> > wrote: > > > On Fri, 2018-11-23 at 09:38 +0100, Oleg Kalnichevski wrote: > > > > > > > ... > > > > > > > > I see no resource leak. The heap looks OK to me. > > > > > > Heap > > > PSYoungGen total 31232K, used 10001K [0x000000076dd00000, > > > 0x0000000771080000, 0x00000007c0000000) > > > eden space 30720K, 32% used > > > [0x000000076dd00000,0x000000076e6bc600,0x000000076fb00000) > > > from space 512K, 6% used > > > [0x0000000771000000,0x0000000771008000,0x0000000771080000) > > > to space 512K, 0% used > > > [0x0000000770f80000,0x0000000770f80000,0x0000000771000000) > > > ParOldGen total 169472K, used 1456K [0x00000006c9600000, > > > 0x00000006d3b80000, 0x000000076dd00000) > > > object space 169472K, 0% used > > > [0x00000006c9600000,0x00000006c976c300,0x00000006d3b80000) > > > Metaspace used 7511K, capacity 7670K, committed 7936K, > > > reserved 1056768K > > > class space used 826K, capacity 921K, committed 1024K, > > > reserved > > > 1048576K > > > > > > The proxy connection times out because it takes the origin server > > > longer than 10 seconds to serve the file. Why that happens I > > > cannot > > > say. There is nothing I can act upon at the moment. > > > > > > Oleg > > > > > > > Gary > > > > Could you please run the server with > > -XX:+HeapDumpOnOutOfMemoryError > > option? Please also consider using Eclipse Memory Analyzer > > https://www.eclipse.org/mat/downloads.php. I will do the same. > > > > Sure! Testing... > > Gary >
Hi Gary I ran 100 Mio requests against the AsyncFileServerExample and took multiple heap dumps in the course of the test run. The AB was running for ~2.5 hours. All message exchanges were successful and the memory footprint remained constant. There might be some sub-optimal intermediate garbage but I certainly could not detect any memory or resource leakage. Again, I cannot fix something I cannot reproduce. This once again might be something Windows specific. Please try to isolate the issue and capture the heap with -XX:+HeapDumpOnOutOfMemoryError option upon OOE. Oleg PS: I am pretty happy with how HttpCore fared so far. --- oleg@ok2c:~/temp$ ab -c 1 -n 100000000 -k http://localhost:8080/one-byte.txt This is ApacheBench, Version 2.3 <$Revision: 1807734 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ ... Server Software: Apache-HttpCore/5.0-beta6-SNAPSHOT Server Hostname: localhost Server Port: 8080 Document Path: /one-byte.txt Document Length: 1 bytes Concurrency Level: 1 Time taken for tests: 8244.365 seconds Complete requests: 100000000 Failed requests: 0 Keep-Alive requests: 100000000 Total transferred: 20700000000 bytes HTML transferred: 100000000 bytes Requests per second: 12129.50 [#/sec] (mean) Time per request: 0.082 [ms] (mean) Time per request: 0.082 [ms] (mean, across all concurrent requests) Transfer rate: 2451.96 [Kbytes/sec] received > > > > > Oleg > > > > > > > > ----------------------------------------------------------------- > > ---- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
