# of requests per second

[Hiroshi Nishida]

Hi,

I have just started using IronWASP.
Is it possible to change the number of requests per second?
Since high load on servers is not desirable, I'd like to reduce the # of requests.

Thank you.

--
Hiroshi Nishida

[Lavakumar Kuppan]

Hi Hiroshi,

 

It is not possible to set the number of requests/second explicitly but you can achieve rate limiting using the 'Scan Threads' settings.

 

If you set this to 1 thread then IronWASP will send a single request, wait for its response to be delivered and only then send the next request.

 

Please refer to the attached image to find out how to configure this.

 

I will try to add requests/second setting as an option in future releases of IronWASP, thanks for bringing it up.

 

Thanks,

Lava

--
You received this message because you are subscribed to the Google Groups "ironwasp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ironwasp+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Hiroshi Nishida]

Lava,

Thanks for the reply.
I'll try with the different numbers of threads.
By the way, I like the speed of IronWASP.
It detects pretty many serious vulnerabilities in short time.
So far, so good.

--
Hiroshi Nishida

[Lavakumar Kuppan]

Thanks for the compliment Hiroshi, I am constantly trying to improve the tool so if you have any concerns with the tool in the future always feel free to bring it up.

 

Thanks,

Lava

--

[Gordon Ma]

Hi Lava,

How do we know how many threads to use?  By default, it's set to 1 thread.  Each scan has taken a long time.  How would we know when the number of threads set is too much?  Is there an alert that would generate error and retry if the # of thread is set too high?  We do have a very fast network here though.  My main concern is will setting too high of a thread cause ironwasp to detect less vulnerability due to the behavior of the server?

Thanks,
Gordon

[Lavakumar Kuppan]

The thread count depends on the speed and performance of your machine and the server. You can set up to 10 threads also if you are on a powerful machine.

 

If IronWASP becomes slow or unresponsive then its an indication to turn down the thread count.

 

If you are using a Session Plugin or Login Recording however then the thread count is automatically set to 1 thread. This is so to make it easy to maintain the authenticated session when performing a scan.

For more options, visit https://groups.google.com/d/optout.