I believe I understand the meaning of these options individually. However, I cannot seem to locate an explanation of how they inter-operate when they are combined together on a single command.
For example, if you are running a command with -threads 4 and -limit 1000 will each of the 4 threads limit themselves to 1000 (effectively a total limit of up to 4000 depending on timing), or will each thread share the total 1000 (effectively giving each thread approx 250 depending on timing)?
Although i have never used that option, I think it is for all the threads. That means that in your example, each thread would get 250 kbps.
This seems like the most sensible approach when implementing this feature.
Also: why is this post in #uncategorized? it should be in #support (i moved it now to the appropriate category)
While I agree that approach seems most sensible, I am not sure it is actually behaving that way in practice. I fear the other interpretation may actually be the case presently.
Let’s wait for the godfather to give the blessing 
Yes, -limit applies to the total transfer speed of all threads. The only caveat is that this limit isn’t honored by the disk-based storage backend (the one implemented in duplicacy_filestorage.go).