Setting the per user limit is nice, but you may want to have a more fine-grained control on how requests are processed by GeoServer. For instance, you may want to have some service, for example, WMS, be given priority over WFS or WCS.
The control flow module lets you set specific limits for each service and you can also configure limits at the request-type level, as we will do in this recipe.
In this recipe, we need to test the control flow module against a higher number of concurrent requests. Unless you're running this recipe on a GeoServer production site, where several real users run ten or more requests each second, you may find it difficult to send many requests by your browser just interactively.