Overriding rate limits

Resource consumption:

There is a balance limit at which an API consumer is disconnected.

For local testing and other purposes, you may want to send a large number of transactions in a short period of time via websocket.

The easiest way is to set your client IP as an administrative IP in the configuration for RPC and/or WS. Something like this, which sets the localhost (127.0.0.1) as administrative:

[port_ws_admin_local]
port = 6006
ip = 0.0.0.0
admin = 127.0.0.1
protocol = ws
send_queue_limit = 500

The admin access bypasses resource limit checks. It also enables things like stopping the server, so it should only be used if you really trust yourself. It also accepts network masks, like 10.0.0.0/8. Here's more detail from the sample config file: https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg#L201

Another way to do this is with something called secure gateway, but it's more complex and requires setting a special HTTP header from the client. https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg#L244

secure_gateway is for when you have clients that you trust enough to provide unlimited resource usage, but you don't want them to have the ability to shut the server down.