Re: [curl-loader-devel] Output understanding
Status: Alpha
Brought to you by:
coroberti
From: Robert I. <cor...@gm...> - 2007-05-06 11:12:37
|
On 5/6/07, Aleksandar Lazic <al-...@no...> wrote: > >If this is a single url, one curl-loader client is mapped 1:1 to > >libcurl handle. Libcurl handle, if my understanding is correct, has up > >to 5 sockets/connections. > > This depend on: HTTP/1.0 or HTTP/1.1 I do not think, that we will support 1.0. > HTTP/1.1 default (=persistant), one $URL/request must not be one > connection. > HTTP/1.1 with 'Connection'-Header close (=no persistant), one > $URL/request one connection. curl-loader has an option -r, which is translated into a libcurl option to arrange a new connection for each request. Another option is to customize "Connection: close", thus a server will close connections. There are also KA options with numbers and timeouts of Keep-Alive, etc > The benchmark tool should be able to handle all this 4 scenarios in a > proper way, also to force some $COMPRESSION-respone from the server, > this is possible with curl-loader, afaik with the CUSTOM_HEADER ;-) Agree. > Well I don't know how modular and flexible the curl-loader is and how > many times you have, I will try to show some options. > > 1.) a new config options e.g.: > > UAS_SESSION_MODE=([Yy]|http1|http1-pers|http11|http11-nopers) > UAS_SESSION_CLIENTS=$NUM > UAS_SESSION_PER_CLIENT_REQUESTS=$NUM <= this is only used if > SESSION_MODE is htt1-pers|http11 > UAS_SESSION_FILE=$PATH <= here are the urls for one session > > 2.) curl-loader assume that all requests to one server should be counted > as session and after the run curl-loader calculate the RPS and > divide it thru the $URLS, it's not the best but I think a possible > way. > > 3.) There is a extra counter and a simple FLAG like > UAS_URL_SESSION=(1|0) and after the run curl-loader calculates based > on this flag and counter how many session are possible. > > 4.) There could be some other ways ;-)) > > I think the httperf is nice for such thing and a good input for some of > this session thing ;-), but the development is stop, it looks to me, and > he is based on select(). Thank you very much, Aleks, I will add it to our TODO list, but don't know, when we will handle it. Currently, we are re-structuring all the approach by going from the sections LOGIN, UAS and LOGOFF to a planar and flexible structure. Current structure does not enable more that a single login and not flexible enough. In a new version each url could be of any type (GET/POST/PUT), contain its own credentials, number of cycles configurable of the url-level, etc. On a later stage we are planning to add customized per-url analyzes of the results based on response code, response body analyzes, conditions, etc. We have also performance issues like memory cached allocations and multi-core/SMP optimization, etc Thank you very much for your suggestions. -- Sincerely, Robert Iakobashvili, coroberti %x40 gmail %x2e com ........................................................... http://curl-loader.sourceforge.net A web testing and traffic generation tool. |