-----Original Message----- From: curl-library [mailto:curl-library-boun...@cool.haxx.se] On Behalf Of Daniel Stenberg Sent: Wednesday, February 12, 2014 17:11 To: libcurl development Subject: RE: Many CLOSE_WAIT when handling lots of URLs
>So there's definately a fix needed here. The documentation could be improved >too as it seems stupid to say that the default is 10 but as soon as you add >one handle, it'll be 4... That means default 10 is make no sense? Can we just set the value as the 4 times of the easy_handle number if this value is not set by user? And what is the meaning if set the maxconnects as 0, means don't cache connection or cache all? I would make a patch after making these clear. >But how many handles have you added then? The maxconnects setting does not >override the number of handles you add. I made more testing on this today. In my test setup, adding 50 eash_handles to a multi-handle. If set the maxconnects <= 50, the cache connections number will always be about 45-50. If set the maxconnects > 50, the cache connections number will be a little greater than maxconnects . So if set maxconnects < easy_handle number, the setting will take no effect. >Can I also remind you that you still haven't provided any good example for us >to repeat this problem so we keep having this discussion where you state vague >things, I see the opposite in the code and we continue without progress. It is >a highly unproductive way of fixing a problem. I think the reproduce condition is keeping the connections number in cache as large enough, for example, >10000. Use the example I send on Jan 6 (http://curl.haxx.se/mail/lib-2014-01/0033.html ) can reproduce it every time. ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
