We are currently using a batchsize of 10 to get the users even so the SE API allows up to 100 which would significantly reduce requests. The reason we do that is because if the tag loading fails say at user 99, the whole chunk goes into the Nirvana even though 99 users were all fine.
We need to do something about that and use a batchsize of 100 then.
We are currently using a batchsize of 10 to get the users even so the SE API allows up to 100 which would significantly reduce requests. The reason we do that is because if the tag loading fails say at user 99, the whole chunk goes into the Nirvana even though 99 users were all fine.
We need to do something about that and use a batchsize of 100 then.