MySQL Bugs: #55128: Throttle feature for localhost connections

Bug #55128	Throttle feature for localhost connections
Submitted:	9 Jul 2010 16:26	Modified:	21 Sep 2012 5:48
Reporter:	ken sands	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	Connector / ODBC	Severity:	S4 (Feature request)
Version:	any	OS:	Any
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any
Tags:	localhost, profiling, throttle

Description:
I'm guessing the odbc (or any other connector) driver is the most appropriate place for this, it'd be nice to have a way to set a throttle, especially for localhost connections so that as a developer there is an easy way to test code is not pulling so much data that it would be slow without actually setting up an instance of mysql on a machine elsewhere on a network/in the world.

There may be other simple ways of doing this, but I've not found it and a throttle option in the connector would seem to be a really nice way for testing. Just a way of trying out how long queries would actually take over a variety of connection speeds.

I admit this seems wrong to have in the standard odbc drivers, but perhaps as a developer plugin or as part of a developer version of the odbc/c/java... driver 

How to repeat:
Run any large select / insert to an instance on localhost. everything seems fine. Test over internet or network to find the network speed bottleneck.
 

Suggested fix:
A throttle response speed parameter so data is fed back within the passed maximum kb/s

This feature is not needed in the ODBC driver because it can be 
easily replaced by specialized software such as NetLimiter 
(check the screenshot):

http://www.netlimiter.com/img/scrshots/nl2shot_limit.png