分析一个简单的goroutine资源池 tunny。
从资源池中获取goroutine并进行处理的逻辑如下:
tunny将goroutine处理单元封装为workWrapper
,由此可以对goroutine的数目进行限制。
workerWrapper.run()作为一个goroutine,内部负责具体事务的处理。其会将一个workRequest
(可以看作是请求处理单元)放入reqChan
,并阻塞等待使用方的调用。workRequest
主要包含两个channel,其中jobChan
用于传入调用方的输入,retChan
用于给调用方返回执行结果。
调用方会从pool的reqChan中获取一个workRequest
请求处理单元,并在workRequest.jobChan
中传参,这样workerWrapper.run()中就会继续进行work.process
处理。处理结束之后将结果通过workRequest.retChan
返回给调用方,然后继续通过reqChan <- workRequest
阻塞等待下一个调用方的处理。
其中workerWrapper.run()中的work
是一个需要用户实现的接口,接口内容如下,最重要的接口是Process(interface{}) interface{}
type Worker interface {
// Process will synchronously perform a job and return the result.
Process(interface{}) interface{}
// BlockUntilReady is called before each job is processed and must block the
// calling goroutine until the Worker is ready to process the next job.
BlockUntilReady()
// Interrupt is called when a job is cancelled. The worker is responsible
// for unblocking the Process implementation.
Interrupt()
// Terminate is called when a Worker is removed from the processing pool
// and is responsible for cleaning up any held resources.
Terminate()
}
tunny中的封装和处理函数并不适合所有的场景,但可以借鉴其核心思想来构造特定场景下的goroutine资源池。