@Technicians,

At this time when increasing the buffer, it's like watching corn grow,

1) For mcm1 each call you get 1 and then it backs off for 121 seconds to call for another until buffer is full, if ever.
2) For ugm1 each call you get 2, same routine
3) For oem1 you get a variable number from 1-5, whatever is maybe available in slots. Interval calling starts with 121 seconds
4) For cep2, no comment, you get as many as you want.
5) For faah/fahv, unknown to me.

When there's none, the interval increments for the projects of choice until some tipping point is reached when it resets. If a work call was successful, the 121 seconds backoff routine repeats. Getting 8 mcm is thus 16 minutes and 8 seconds plus dl time, if lucky.

If there are many 'high server load' messages, then would this not be one of the main causes? For sure, can't load up quick and go offline. The reason of this way of operation is escaping me, is there some strategy in this benefiting the volunteer, for instance give more diverse work supply, but piece-meal? Certainly it used to be like 10-20 per fetch request for general available projects, which mcm1 to me would be.

Tia for your explanation.