Welcome to MTurk Crowd

Work on Amazon Mechanical Turk, learn from the best, and have fun doing it. Join the crowd today!

Sign Up

Throttling 2.0

Discussion in 'MTurk Help & Resources' started by Kadauchi, Jul 24, 2017.

  1. Kadauchi

    Expand Collapse
    Well-Known Member

    • Crowd Pleaser
    • Master Pleaser
    Jan 12, 2016
    In April 2016 Mturk added a new "feature" now referred to as Throttling.

    What happens is when too many HITs have been accepted out of the same batch, Mturk will prevent additional workers from accepting more until the currently accepted HITs are submitted, returned or expired.

    A recent change (2017) to how throttling works now makes it so you can no longer preview a batch that is being throttled. This change means using a PanthA to try and get around throttling no longer works, rendering it useless and a waste of page requests.

    Lets say that the limit to accepted HITs out of a single batch is 100.

    Customer Interest throttle doesn't seem bad because of the shorter completion times and short timer. This means HITs have a quick turnover rate allowing workers to more frequent accept work from the batch..

    PicsFromAbove throttle seems bad because of the longer completion times and long timer. This means HITs idle in a workers queue a long time preventing other workers from being able to accept work from the batch.

    Disclaimer: This has not been confirmed by Mturk so technically it is speculation. That being said, I am confident in the above statements.
  2. PatsyMI

    Expand Collapse
    New Member

    Jul 14, 2018
    Thank you. I am new to MTurk and have many questions, and this was one. I did not know if it was me - that I was not able to access the HIT because of some fault (possibly browser? or speed) on my part that made it impossible for me to work on the HIT. Each time I see a question that sort of resembles a problem that I am having - even if it's not exactly as I would word it - it helps me understand the MTurk system. So thanks again for your explanation.