According to the README:
> Use the second parameter of `server.NewWorker` to limit the number of concurrently running
> worker.Process() calls (per worker). Example: 1 will serialize task execution while 0 makes
> the number of concurrently executed tasks unlimited (default).
This change will set the concurrency to 2 * num CPUs when concurrency = 0. While it isn't "unlimited", it is neverthe a practical choice for most workloads (mixed CPU, I/O) and better than 1. This change should make the behavior more consistent with the doc.
Should also fix #535
Co-authored-by: Charles Chan <charles.wh.chan@users.noreply.github.com>
Co-authored-by: Richard Knop <RichardKnop@users.noreply.github.com>