Open xehu opened 4 years ago
@xehu Does this stop batches from running? Or just stop us from easily sending bonuses etc?
As mentioned on basecamp. The main courses of action seem to be:
Other options? Other analysis on the options we have?
This does not seem to stop batches from running. The only harm is that it stops us from easily bonusing workers who complain (it seems that, on occasion, workers are still incorrectly being bonused only $8.80). It also stops an easy search in case people email about finding their link (I'd have to call the users API directly instead).
Other thought: Is it possible to pre-load the users page somehow so that it doesn't have to do it every time? Or alternatively, it is possible to split it into clean subgroups - for example, only load people with hasBanged = true or hasBanged = false, such that we reduce the number of users that we have to load?
Good to hear that its not going to block you from running! We can set up an alternative bonus plan until we have this working. Ping me if you want to chat about that.
I like the idea of loading separately, e.g., /users
for willbang
and /pastusers
for hasbanged
. That seems like it would be simple and would require fewer changes, however it is also only a short-term solution — we will still end up with a lot of people on both those lists. I think pagination is still a stronger long-term solution.
Thoughts?
Currently, the db of users is so large that the Users Page does not consistently load (and in my experience, is not really loading at all):