|
|
Economy Traffic / From $9.9 per month. If you are looking for cheap, bulk trafic source, our Economy Packages are the perfect solution for you. All traffic is accepted by Google Analytics, Piwik, Kissmetrics, Clicky, Gauges, Woopra, and other popular visitor tracking systems. This kind of traffic is also known as Alexa or Adult Traffic.
Recent Searches |
davinci, total network inventory, restoro, manageengine, sediv, zipstar, nitro pdf, squeez, ‹› byclouder data recovery pro, machinarium, sims 4, driverdoc, cam, cammask, virtual dj, repro, u-he, easeus mobimover, nordvpn, getmydrivers, coreldraw, filmora9, disk drill 2.0.0.339, atomix, traktor, the sims 4 tiny living , fl studio , winx hd, magix vidéo deluxe 2013 premium, disk drill 2.0.0339, save wizard, quicken, glary utilities, smadav 2020, tableau, tableau desktop, cubase , avg 20.2.3116, fonepaw, cubase 9, geneatique, photo collage maker, vpn, downloader, portforward, fd, nobel, blue sky plan, abby fine reader, avast, |
A simple traffic generator for network experiments.
The server listens for incoming requests, and replies with a flow with the requested size (using the requested DSCP value & sending at the requested rate) for each request.
The client establishes persistent TCP connections to a list of servers and randomly generates requests over TCP connections according to the client configuration file. If no available TCP connection, the client will establish a new one. Currently, we provide two types of clients: client and incast-client for dynamic flow experiments. For client, each request only consists of one flow (fanout = 1). For incast-client, each request can consist of several synchronized incast-like flows. A request is completed only when all its flows are completed.
In the client configuration file, the user can specify the list of destination servers, the request size distribution, the Differentiated Services Code Point (DSCP) value distribution, the sending rate distribution and the request fanout distribution, .
In the main directory, run make, then you will see client, incast-client, simple-client (generate static flows for simple test), server and some python scripts in ./bin.
In the main directory, do following operations:
Example:
-p : the TCP port that the server listens on (default 5001)
-v : give more detailed output (verbose)
-d : run the server as a daemon
-h : display help information
Example:
-b : desired average RX bandwidth in Mbits/sec
-c : configuration file which specifies workload characteristics (required)
-n : number of requests (instead of -t)
-t : time in seconds to generate requests (instead of -n)
-l : log file with flow completion times (default flows.txt)
-s : seed to generate random numbers (default current system time)
-r : python script to parse result files
-v : give more detailed output (verbose)
-h : display help information
Note that you need to specify either the number of requests (-n) or the time to generate requests (-t). But you cannot specify both of them.
Example:
Same as client except for -l
The client configuration file specifies the list of servers, the request size distribution, the Differentiated Services Code Point (DSCP) value distribution, the sending rate distribution and the request fanout distribution (only for incast-client). We provide several client configuration files as examples in ./conf directory.
The format is a sequence of key and value(s), one key per line. The permitted keys are:
There must be one request size distribution file, present at the given path,which specifies the CDF of the request size distribution. See 'DCTCP_CDF.txt' in ./conf directoryfor an example with proper formatting.
For each request, the client chooses a DSCP value with a probability proportional to the weight. The traffic of the request and the corresponding response(s) will be marked with this DSCP value. If the user does not specify the DSCP distribution, the DSCP value is always 0 for all requests. This feature can be used to create multiple classes of traffic (e.g., section 5.1.2 of MQ-ECN paper).
For each request, the client chooses a rate with a probability proportional to the weight. To enforce the sending rate, the sender will add some delay at the application layer. Note that 0Mbps indicates no rate limiting. If the user specifies very low sending rates, the client may achieve a much lower average RX throughput in practice, which is undesirable. If the user does not specify the sending rate distribution, the sender will not rate-limit the traffic. We suggest the user simply disabling this feature except for some special scenarios.
For each request, the client chooses a fanout with a probability proportional to the weight. For example, with the above configuration, half the requests have fanout 1, and 20% have fanout 8. If the user does not specify the fanout distribution, the fanout size is always 1 for all requests.
##OutputA successful run of client creates a file with flow completion time results. A successful run of incast-client creates two files with flow completion time results and request completion time results, respectively. You can directly use ./bin/result.py to parse these files.
/generate-ssh-key-via-git-bash.html. In files with flow completion times, each line gives flow size (in bytes), flow completion time (in microseconds), DSCP value, desired sending rate (in Mbps) and actual per-flow goodput (in Mbps).
In files with request completion times, each line gives request size (in bytes), request completion time (in microseconds), DSCP value, desired sending rate (in Mbps), actual per-request goodput (in Mbps) and request fanout size.
##ContactFor questions, please contact Wei Bai (http://sing.cse.ust.hk/~wei/).
##Publications