06/04 - Simple Question Sunday ft. NBadger's 100 GIFs in 100 Days Journy

Are you continuing to run pandas/scrapers while trying to work on them? I swap to an offline (logged out) keyword scraper when batches drop so my PRE pool is totally freed up.

Between worker/www, you shouldn't be hitting PREs that much

You theoretically have room for 1,800 HITs/hr before PREs would be an issue (assuming perfect catches, which obviously isn't possible), unless you're running other stuff simultaneously. Throttling hurts, but it shouldn't*** be 600 HITs/hr hurt.

 

~4 mins

 

How do you do this/what's the benefit?

 

These Pins aren't getting grabbed with Auto-reload .. oh my.

 

I usually have OW (4secs) and HF (> $1, 1 sec) on the worker side and a 6seconds Hit Scraper and PC 980ms on mturk. When CI or other batches drop I switch off HitScraper and PC, I open PC on worker and panda the batch from there: this is the only way I don't get PRE on MTurk. I think I should double check even my other scripts to see which ones generate PRE, but I hope that disabling Queue Fixer will make the trick!
I cannot get used to HitScraper on Incognito mode because, even if I'm able to send HITs from there to the logged profile, it doesn't show the number of HITs, so it's practically useless for the purpose I'm using it -> find batches.
I think that working on two windows, one logged and one in incognito, might be a very good solution if getting rid of Queue Fixer won't reduce my PREs, thanks again for both these hints! ^_^

 

Slow Down!
It looks like you already have tasks assigned. Please complete those tasks first before taking more work. This allows us to more equitably distribute tasks to our workers. If you don't have access to your previously assigned tasks, do not worry. Those tasks will be automatically abandoned after thirty minutes, so please check in then. Thanks for your cooperation!

 

Ah.. so it was you who ate all my pins

 

I don't know how to do this but I suspect the benefit is that his PRE pool is freed up.

 

I wrote my own script for this, but I assume its possible w/ hit scraper.

The benefit is I'm not losing my page requests to watching mTurk when I'm trying to work on mTurk. What good is knowing work is there if you can't submit it because you're worried about what other work might come up?

If something more profitable pops I'll still know it and can switch over, but I'm only looking for known quantities that are more valuable than what I already have sitting in front of me when work is up.

But even without it, I'd still turn off everything else and work over fighting with my own scraper to be able to submit HITs.

 

Hidden US location QUAL because it asks for US Zip Code.

 

Hi, i'll like to ask, are any of you guys non-US who are part of the high earners here?
I'm thinking I can't make much if i'm not from the U.S.

 

It's definitely a factor. A lot of stuff is US only. But I'm still new at this so I don't have a definite answer to this.

EDIT: Not a a high earner

 

We have some Canadians who are making a couple hundred a week. Maybe a few from the UK who do okay. Otherwise, it is significantly lower as you're usually going to be blocked from most surveys and a decent amount of batches.

 

Greetings from Amazon Mechanical Turk,
The following is a summary of activity for your Mechanical Turk account for the week ending Jun 03, 2017.
Your HIT activity for this week:
- Number of HITs submitted: 660
Approvals and payments that occurred this week:
- Number of HITs approved: 1,000
- Number of HITs rejected: 0
- HIT reward earned: $106.18
- Total Amount earned this week: $106.18

Long way to go looking at some of you guys

 

Ok..so for question day...someone explain PRE's to me

 

Page Request Errors. Amazon limits the amount of things you can be doing at once. If you click the link in your question, the wiki will explain it better than I can.

 

Hello

 

Basically in order to keep things "fair" (and probably some cost concerns as well as far as servers go) mTurk will only let you load their website a certain amount of times before telling you to go away.

This is so that folks who have a lot of computing power can't just pound the website and take all the work (and other resources, effectively ddos'ing mTurk).

Your ping and the accuracy of whatever tools you're using to load mTurk affect the perceived rate of PREs you get. Common ranges say 1 request per 700ms-1s for a logged in account, 1 request per 400-600ms for a logged out request.

You want to avoid PREs because you end up locked out for upwards of 3 seconds, which means you could have loaded the site 3-5 times more than if you just backed off the original requests. PREs scale somewhat exponentially since the more requests you put in the more requests will end in failure during your "lockout" period.

Overall they're good for the mTurk community, bad for individuals with lots of resources/know-how.

 

Heya Welcome to TH!