I cannot believe this. When doing the previous memory leak "tests" I
overlooked the fact that I made a change to my test-config.tcl a LONG
while ago when I was chasing down another bug (see SF Bug #1082401).
Yes, my test-config.tcl had "ns_param connsperthread 1" set! There's
obviously a bug when that is set, and obviously one of them includes a
32K memory leak.
I've removed the config line, and here's what I get:
$ ps -Ao pid,vsz,rss,comm | egrep "PID|7479"
PID VSZ RSS COMMAND
7479 13972 2856 nsd
$ ab -c 25 -n 10000 http://$hostname:8000/
This is ApacheBench, Version 1.3d <$Revision: 1.67 $> apache-1.3
...
Concurrency Level: 25
Time taken for tests: 4.723 seconds
Complete requests: 10000
Failed requests: 0
Broken pipe errors: 0
Non-2xx responses: 10000
Total transferred: 7220000 bytes
HTML transferred: 5480000 bytes
Requests per second: 2117.30 [#/sec] (mean)
Time per request: 11.81 [ms] (mean)
Time per request: 0.47 [ms] (mean, across all concurrent requests)
Transfer rate: 1528.69 [Kbytes/sec] received
...
$ ps -Ao pid,vsz,rss,comm | egrep "PID|7479"
PID VSZ RSS COMMAND
7479 14244 3000 nsd
Negligible memory growth (300K for 10K requests) -- as you'd totally
expect.
SO, this begs the question: The people who are reporting memory leaks,
do you have "connsperthread" set to anything in your config files?
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
