Thank you for the number.
It sure is the share rate target. Sending results of one's work is the same as sending shares. :-)
Share rate would depend on the speed of my miners only if there were no VarDiff. The purpose of VarDiff is to set a reasonable share rate for each worker, preventing overloading and incidentally protecting bandwidth, yes. :-)
Shares have different values for different target settings, but they're still shares...
I think we are simply interpreting the question in different ways. There is a target for the number of share submissions - around 20 per minute - but not for the actual number of resulting shares, i.e. submissions x difficulty, which is how I understood the question.
In other words, you suspect me of posting dumb questions. :-)
I understand the matter quite well, no need for repeating.
Resulting shares should read
resulting diff 1 shares in your interpretation, but I've never said anything like that. Never mentioned
resulting shares, diff 1 shares or
submissions x difficulty. It's you who's pushing those items here.
My question applied to the rate of submitted shares, i.e. those shares the worker submits to the pool, whatever their value can be. It's quite clear from the question itself, I was asking about the target value of share rate for a particular instance of VarDiff, which is quite a common & reasonable question.
