Re: [curl-loader-devel] Have you submitted your memory reduction patchs to upstream curl
Status: Alpha
Brought to you by:
coroberti
From: Robert I. <cor...@gm...> - 2007-04-27 04:37:45
|
Hi Yusuf, On 4/27/07, Yusuf Goolamabbas <yu...@ou...> wrote: > I've been following your curl-loader project (I haven't installed it as > yet since I still have to understand fully the impact of this statement > > 'Each client performs loading from its own source IP-address' > In particular, what is the impact on a kernel stack on creating 10,000 > IP's ? I have not learned the issue in depth, but even the PC with 500 M memory does not demo any problems with that. My guess, that each address takes 5-6 bytes of the kernel memo. Y can browse the lxr linux kernel code and search for the secondary IP storage done bia netlink system. > I am particularly interested in the hyper-mode creating lots of virtual users > In your recent 0.30 release you mentioned a reduction in memory usage by > patching libcurl. Is this patch upstream ? There is a patch, which is took upstream and cuts 16K, beyond of this we are bulding libcurl with buffers sized 8k, not 16K. > As such are you now mandating > that curl-loader should not be linked with system supplied > libcurl/libevent and should only be used with the the supplied > libcurl/libevent We are using our own building (with optimization) and at least 1 patch of libcurl, which is not mainstream. Yes, we are mandating it by building them as a static libraries and linking them statically in order: a) to have a unified building system; b) not to mess with the versions shipped on various linux distros. c) to have an option to patch; d) to have an option to optimize; e) not to intervene (destroy, mess) user-used linux. Actually, there is no impact of this on your linux distro. > > Also, with 10,000 clients @ 35K each would be a memory consumption of > 350MB. Seems a tad high. Has there been any comment from the libcurl > developers on how to reduce this even further ? Y can enter our Makefile and change an option passed to ./configure CFLAGS -DCURL_MAX_WRITE_SIZE=8192 to e.g. 4096. Thus, you will cut 8K more, but test the impact on your performance. Still, you can do it with curl mainstream cvs version and recent daily snapshot. Please, direct all questions to cur...@li..., subscribe however first. -- Sincerely, Robert Iakobashvili, coroberti %x40 gmail %x2e com ................................................................... Navigare necesse est, vivere non est necesse ................................................................... http://curl-loader.sourceforge.net An open-source HTTP/S, FTP/S traffic generating, and web testing tool. |