Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Tool to check Concurrent Visitors handling ability
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Tool to check Concurrent Visitors handling ability

Hey Guys, I'm looking for a tool that can help me to check the number of concurrent visitors my server can handle so that i can put focus on optimising the server better. Thanks :)

P.S.: There are certain tools in the past like blitz.io but i don't remember which one works the best as of now.

Comments

  • LeviLevi Member

    Apache Bench should suffice.

    Another way is to look for booter service and DDoS your-self ( this one probably not legal).

    Thanked by 1Bertie
  • ab -n 100 -c 10 website-url

    i'm getting this:

    ab: invalid URL
    Usage: ab [options] [http[s]://]hostname[:port]/path
    Options are:
    -n requests Number of requests to perform
    -c concurrency Number of multiple requests to make at a time
    -t timelimit Seconds to max. to spend on benchmarking
    This implies -n 50000
    -s timeout Seconds to max. wait for each response
    Default is 30 seconds
    -b windowsize Size of TCP send/receive buffer, in bytes
    -B address Address to bind to when making outgoing connections
    -p postfile File containing data to POST. Remember also to set -T
    -u putfile File containing data to PUT. Remember also to set -T
    -T content-type Content-type header to use for POST/PUT data, eg.
    'application/x-www-form-urlencoded'
    Default is 'text/plain'
    -v verbosity How much troubleshooting info to print
    -w Print out results in HTML tables
    -i Use HEAD instead of GET
    -x attributes String to insert as table attributes
    -y attributes String to insert as tr attributes
    -z attributes String to insert as td or th attributes
    -C attribute Add cookie, eg. 'Apache=1234'. (repeatable)
    -H attribute Add Arbitrary header line, eg. 'Accept-Encoding: gzip'
    Inserted after all normal header lines. (repeatable)
    -A attribute Add Basic WWW Authentication, the attributes
    are a colon separated username and password.
    -P attribute Add Basic Proxy Authentication, the attributes
    are a colon separated username and password.
    -X proxy:port Proxyserver and port number to use
    -V Print version number and exit
    -k Use HTTP KeepAlive feature
    -d Do not show percentiles served table.
    -S Do not show confidence estimators and warnings.
    -q Do not show progress when doing more than 150 requests
    -l Accept variable document length (use this for dynamic pages)
    -g filename Output collected data to gnuplot format file.
    -e filename Output CSV file with percentages served
    -r Don't exit on socket receive errors.
    -m method Method name
    -h Display usage information (this message)
    -I Disable TLS Server Name Indication (SNI) extension
    -Z ciphersuite Specify SSL/TLS cipher suite (See openssl ciphers)
    -f protocol Specify SSL/TLS protocol
    (SSL2, TLS1, TLS1.1, TLS1.2 or ALL)

  • donkodonko Member

    https://loader.io/ but allow only 1 minute free

  • Webdock_ioWebdock_io Member, Host Rep

    We wrote a guide on how to use ApacheBench and interpret the results:

    https://webdock.io/en/docs/optimizing-performance/how-benchmark-your-server-apachebench

    AB is - in my mind - the best way to generalize and abstract away a lot of the problems with benchmarking a VPS. You can measure CPU, BW, IOPS and whatnot all day long, but all those differing numbers won't really tell you about bottlenecks or how many pages/sec or concurrent visits a server can really handle.

    Here AB shines and really helps out.

    BTW I think ab failed for you as it always expects a trailing slash in the URL you provide

Sign In or Register to comment.