Dynamic throttling based on target system CPU load

Hi What Lies Beneath -- the case I'm referring to is when an entire cluster is busy -- that I start throttling the whole cluster. Balancing between machines is working reasonably well in my case. Do the solutions you mention address that? They seemed more like ways to distribute load to an appropriately sized cluster. What's going on here is that sometimes there are "bad guys" that flood us with traffic that they haven't asked us to size for -- often due to configuration issues on their side etc.

Here's the trick:

- I'd like to change the throttle dynamically with time -- the simplest way to understand is that the backend system is doing more than real-time processing (e.g. some batch jobs etc), and when those things are loading up the system (which doesn't occur on a regular schedule), I'd like to be able to start reducing the amount of traffic allowed to hit the service

- Ideally I'd allow sticky sessions to continue using the service, so I'd throttle sessions rather than connections. But if connections is all I can accomplish, that would still be better than what I have.

- This is a multi-tenant system, and so even more ideally, I'd love to track the tenant's usage patterns, and when one tenant is being a "bad guy" to throttle him more than others

Thanks,

Dusty