Query.setLimit() performance problem

I've encounter a substantial slowdown in my code when using a view in combination with a query. It seems that setting the limit (other setters have not been tried, but are likely to show similar behaviour) will eventually call net.spy.memcached.util.StringUtils#isJsonObject(). In 2.10.5 and earlier, this method will use 'new Integer()/catch NumberFormatException' to test if the passed argument can be parsed to an Integer object. However, the number of thrown and caught exceptions was severely limiting performance on my setup.

Removing the setLimit() call on my Query object resulted in a threefold increase in performance (from 600 to 1900 rps).

Original SpyMemcached issue: http://code.google.com/p/spymemcached/issues/detail?id=298