Injecting latency into application requests?

The after command is non blocking. It will fire and allow the connection to continue processing as normal, so there would be no inherent latency. That is, in fact, the entire purpose of the after command: to allow you to continue processing a session while assigning some task to be done at a specified time. To actually pause the connection and add latency, you need to do something that will suspend things, like a collect, a loop, etc. A collect is likely the safest means is all.

 

 

I still want to make sure everyone knows this practice is generally a very bad thing, as it can slow things down that you aren't expecting...but there you have it. ;)

 

 

Colin