Abstract: Improved solutions for noisy neighbor throttling (1) ensure that global capacity is not exceeded, (2) allow use of idle resources without a need to specify exceptions, and (3) focus throttling on misbehaving actors (“noise neighbors”) first, while avoiding throttling well-behaved ones. A trigger point is set for initiating throttling for a server, and requests are received from multiple clients. In each timeslot, a total request count and a client-specific request count is determined. The client-specific request counts are sorted in descending order in a list. Efficient single-swap sorting may be used for speed. If the total request count meets the trigger point during a timeslot, the client with the highest request count is readily-identifiable at the top of the sorted list, and that client is throttled. If, while that client is still being throttled, the trigger is hit again and that client still tops the list, the throttling is enhanced.