2018-05-19 04:13:39 +03:00
# ants
2018-05-19 04:15:54 +03:00
2019-01-25 16:25:42 +03:00
< div align = "center" > < img src = "https://user-images.githubusercontent.com/7496278/51748488-8efd2600-20e7-11e9-91f5-1c5b466dcca1.jpg" / > < / div >
2018-05-19 04:15:54 +03:00
2018-05-20 18:34:34 +03:00
< p align = "center" > A goroutine pool for Go< / p >
2018-05-20 18:35:28 +03:00
2018-06-29 05:45:58 +03:00
[![Build Status][1]][2]
2018-07-15 17:45:55 +03:00
[![codecov][3]][4]
2018-06-29 05:45:58 +03:00
[![goreportcard for panjf2000/ants][5]][6]
2018-07-15 17:45:55 +03:00
[![godoc for panjf2000/ants][7]][8]
[![MIT Licence][9]][10]
2018-05-20 18:27:20 +03:00
2019-01-25 15:57:38 +03:00
[中文 ](README_ZH.md ) | [Project Tutorial ](http://blog.taohuawu.club/article/goroutine-pool )
2018-06-08 09:50:56 +03:00
2019-01-25 18:03:05 +03:00
Library `ants` implements a fixed capacity goroutine-pool for managing and recycling a massive number of goroutines, allowing developers to limit the number of goroutines that created in your concurrent programs.
2018-05-20 18:27:20 +03:00
## Features:
2018-05-21 05:45:25 +03:00
- Automatically managing and recycling a massive number of goroutines.
2019-01-25 18:03:05 +03:00
- Periodically purging overdue goroutines.
2018-07-09 11:32:33 +03:00
- Friendly interfaces: submitting tasks, getting the number of running goroutines, readjusting capacity of pool dynamically, closing pool.
2019-01-25 18:03:05 +03:00
- Handle panic gracefully to prevent programs from crash.
2018-05-21 05:45:25 +03:00
- Efficient in memory usage and it even achieves higher performance than unlimited goroutines in golang.
2018-05-20 18:27:20 +03:00
2019-01-26 21:07:33 +03:00
## Tested in the following Golang versions:
- 1.8.x
- 1.9.x
- 1.10.x
- 1.11.x
- master
2018-05-20 18:27:20 +03:00
## How to install
``` sh
go get -u github.com/panjf2000/ants
```
Or, using glide:
``` sh
glide get github.com/panjf2000/ants
```
## How to use
2019-01-25 18:03:05 +03:00
Just take a imagination that your program startovers a massive number of goroutines, from which a vast amount of memory will be consumed. To mitigate that kind of thing, all you need to do is to import `ants` package and submit all your tasks to a default pool with fixed capacity created when `ants` has been imported:
2018-05-20 18:27:20 +03:00
``` go
package main
import (
"fmt"
"sync"
2018-05-26 03:42:10 +03:00
"sync/atomic"
2018-07-02 09:45:25 +03:00
"time"
2018-05-26 03:42:10 +03:00
"github.com/panjf2000/ants"
2018-05-20 18:27:20 +03:00
)
2018-05-26 03:42:10 +03:00
var sum int32
2018-12-03 06:23:37 +03:00
func myFunc(i interface{}) {
2018-07-02 09:45:25 +03:00
n := i.(int32)
atomic.AddInt32(& sum, n)
2018-05-26 03:42:10 +03:00
fmt.Printf("run with %d\n", n)
}
2018-12-03 06:23:37 +03:00
func demoFunc() {
2018-05-26 03:42:10 +03:00
time.Sleep(10 * time.Millisecond)
2018-05-20 18:27:20 +03:00
fmt.Println("Hello World!")
}
func main() {
2018-07-02 09:45:25 +03:00
defer ants.Release()
2018-05-26 03:42:10 +03:00
runTimes := 1000
2018-12-06 19:33:43 +03:00
// Use the common pool
2018-05-20 18:27:20 +03:00
var wg sync.WaitGroup
for i := 0; i < runTimes ; i + + {
wg.Add(1)
2018-12-01 14:41:02 +03:00
ants.Submit(func() {
2018-05-26 03:42:10 +03:00
demoFunc()
2018-05-20 18:27:20 +03:00
wg.Done()
})
}
wg.Wait()
2018-05-26 03:42:10 +03:00
fmt.Printf("running goroutines: %d\n", ants.Running())
fmt.Printf("finish all tasks.\n")
2018-12-06 19:33:43 +03:00
// Use the pool with a function,
// set 10 to the size of goroutine pool and 1 second for expired duration
2018-12-01 14:41:02 +03:00
p, _ := ants.NewPoolWithFunc(10, func(i interface{}) {
2018-05-26 03:42:10 +03:00
myFunc(i)
wg.Done()
})
2018-07-02 09:45:25 +03:00
defer p.Release()
2018-12-06 19:33:43 +03:00
// Submit tasks
2018-05-26 03:42:10 +03:00
for i := 0; i < runTimes ; i + + {
wg.Add(1)
2018-07-02 09:45:25 +03:00
p.Serve(int32(i))
2018-05-26 03:42:10 +03:00
}
wg.Wait()
fmt.Printf("running goroutines: %d\n", p.Running())
fmt.Printf("finish all tasks, result is %d\n", sum)
2018-05-20 18:27:20 +03:00
}
```
2018-12-07 03:57:47 +03:00
## Integrate with http server
2018-12-02 08:48:44 +03:00
```go
package main
import (
"io/ioutil"
"net/http"
"github.com/panjf2000/ants"
)
2018-12-02 16:53:43 +03:00
type Request struct {
Param []byte
Result chan []byte
}
2018-12-02 08:48:44 +03:00
func main() {
pool, _ := ants.NewPoolWithFunc(100, func(payload interface{}) {
2018-12-03 05:13:53 +03:00
request, ok := payload.(*Request)
2018-12-02 08:48:44 +03:00
if !ok {
2018-12-03 09:31:49 +03:00
return
2018-12-02 08:48:44 +03:00
}
reverseParam := func(s []byte) []byte {
for i, j := 0, len(s)-1; i < j ; i , j = i+1, j-1 {
s[i], s[j] = s[j], s[i]
}
return s
2018-12-02 16:53:43 +03:00
}(request.Param)
2018-12-02 08:48:44 +03:00
2018-12-02 16:53:43 +03:00
request.Result < - reverseParam
2018-12-02 08:48:44 +03:00
})
defer pool.Release()
http.HandleFunc("/reverse", func(w http.ResponseWriter, r *http.Request) {
2018-12-02 16:53:43 +03:00
param, err := ioutil.ReadAll(r.Body)
2018-12-02 08:48:44 +03:00
if err != nil {
http.Error(w, "request error", http.StatusInternalServerError)
}
defer r.Body.Close()
2018-12-03 05:13:53 +03:00
request := & Request{Param: param, Result: make(chan []byte)}
2018-12-02 16:53:43 +03:00
2018-12-06 19:33:43 +03:00
// Throttle the requests traffic with ants pool. This process is asynchronous and
2018-12-02 08:48:44 +03:00
// you can receive a result from the channel defined outside.
2018-12-02 16:53:43 +03:00
if err := pool.Serve(request); err != nil {
2018-12-02 08:48:44 +03:00
http.Error(w, "throttle limit error", http.StatusInternalServerError)
}
2018-12-02 16:53:43 +03:00
w.Write(< -request.Result )
2018-12-02 08:48:44 +03:00
})
http.ListenAndServe(":8080", nil)
}
```
2018-12-06 19:33:43 +03:00
## Submit tasks
2018-05-26 12:26:36 +03:00
Tasks can be submitted by calling `ants.Submit(func())`
2018-05-21 07:45:15 +03:00
```go
2018-12-02 08:48:44 +03:00
ants.Submit(func(){})
2018-05-21 07:45:15 +03:00
```
2018-12-06 19:33:43 +03:00
## Customize limited pool
2019-01-25 18:03:05 +03:00
`ants` also supports customizing the capacity of pool. You can call the `NewPool` function to instantiate a pool with a given capacity, as following:
2018-05-20 18:27:20 +03:00
``` go
2018-12-06 19:33:43 +03:00
// Set 10000 the size of goroutine pool
2018-07-24 16:53:34 +03:00
p, _ := ants.NewPool(10000)
2018-12-06 19:33:43 +03:00
// Submit a task
2018-12-02 08:48:44 +03:00
p.Submit(func(){})
2018-05-20 18:27:20 +03:00
```
2018-12-06 19:33:43 +03:00
## Tune pool capacity
2019-01-26 19:05:51 +03:00
You can tune the capacity of `ants` pool at any time with `Tune(int)` :
2018-05-20 18:27:20 +03:00
``` go
2019-01-26 19:05:51 +03:00
pool.Tune(1000) // Tune its capacity to 1000
pool.Tune(100000) // Tune its capacity to 100000
2018-05-20 18:27:20 +03:00
```
2019-01-25 18:03:05 +03:00
Don't worry about the synchronous problems in this case, the function here is thread-safe (or should be called goroutine-safe).
2018-05-20 18:27:20 +03:00
2019-01-26 19:05:51 +03:00
## Release Pool
```go
pool.Release()
```
2018-05-20 18:27:20 +03:00
## About sequence
2019-01-25 18:03:05 +03:00
All the tasks submitted to `ants` pool will not be guaranteed to be addressed in order, because those tasks scatter among a series of concurrent workers, thus those tasks are executed concurrently.
2018-05-20 18:27:20 +03:00
## Benchmarks
2018-07-06 15:39:23 +03:00
```
2019-01-26 21:07:33 +03:00
OS: macOS High Sierra
Processor: 2.7 GHz Intel Core i5
Memory: 8 GB 1867 MHz DDR3
2018-07-06 15:39:23 +03:00
2019-01-26 21:07:33 +03:00
Go Version: 1.9
2018-07-06 15:39:23 +03:00
```
2019-01-22 09:14:17 +03:00
< div align = "center" > < img src = "https://user-images.githubusercontent.com/7496278/51515466-c7ce9e00-1e4e-11e9-89c4-bd3785b3c667.png" / > < / div >
2018-05-20 18:27:20 +03:00
2019-01-25 18:03:05 +03:00
In that benchmark-picture, the first and second benchmarks performed test cases with 1M tasks and the rest of benchmarks performed test cases with 10M tasks, both in unlimited goroutines and `ants` pool, and the capacity of this `ants` goroutine-pool was limited to 50K.
2018-05-20 18:34:34 +03:00
2018-12-05 19:26:28 +03:00
- BenchmarkGoroutine-4 represents the benchmarks with unlimited goroutines in golang.
2018-05-20 18:27:20 +03:00
2018-12-05 19:50:33 +03:00
- BenchmarkPoolGroutine-4 represents the benchmarks with a `ants` pool.
2018-05-20 18:27:20 +03:00
2019-01-25 18:03:05 +03:00
The test data above is a basic benchmark and more detailed benchmarks are about to be uploaded later.
2018-05-20 18:27:20 +03:00
2018-05-27 17:41:55 +03:00
### Benchmarks with Pool
2019-01-22 09:14:17 +03:00
![](https://user-images.githubusercontent.com/7496278/51515499-f187c500-1e4e-11e9-80e5-3df8f94fa70f.png)
2018-05-27 17:41:55 +03:00
2019-01-25 18:03:05 +03:00
In above benchmark picture, the first and second benchmarks performed test cases with 1M tasks and the rest of benchmarks performed test cases with 10M tasks, both in unlimited goroutines and `ants` pool, and the capacity of this `ants` goroutine-pool was limited to 50K.
2018-05-27 17:41:55 +03:00
2019-01-25 18:03:05 +03:00
**As you can see, `ants` can up to 2x faster than goroutines without pool (10M tasks) and it only consumes half the memory comparing with goroutines without pool. (both 1M and 10M tasks)**
2018-05-27 17:41:55 +03:00
### Benchmarks with PoolWithFunc
2019-01-22 09:14:17 +03:00
![](https://user-images.githubusercontent.com/7496278/51515565-1e3bdc80-1e4f-11e9-8a08-452ab91d117e.png)
2018-05-27 17:41:55 +03:00
2019-01-25 18:03:05 +03:00
### Throughput (it is suitable for scenarios where asynchronous tasks are submitted despite of the final results)
2018-05-27 17:41:55 +03:00
2018-07-22 04:32:55 +03:00
#### 100K tasks
2018-05-27 17:41:55 +03:00
2019-01-22 09:14:17 +03:00
![](https://user-images.githubusercontent.com/7496278/51515590-36abf700-1e4f-11e9-91e4-7bd3dcb5f4a5.png)
2018-05-27 17:41:55 +03:00
2018-07-22 04:32:55 +03:00
#### 1M tasks
2018-05-27 17:41:55 +03:00
2019-01-22 09:14:17 +03:00
![](https://user-images.githubusercontent.com/7496278/51515596-44617c80-1e4f-11e9-89e3-01e19d2979a1.png)
2018-05-27 17:41:55 +03:00
2018-07-22 04:32:55 +03:00
#### 10M tasks
2018-05-27 17:41:55 +03:00
2019-01-22 09:14:17 +03:00
![](https://user-images.githubusercontent.com/7496278/51515615-5e9b5a80-1e4f-11e9-8816-66a935c32b05.png)
2018-05-27 17:41:55 +03:00
2019-01-25 18:03:05 +03:00
There was only the test case with `ants` pool because my program crashed when it reached 10M goroutines without using a pool.
2018-05-27 17:41:55 +03:00
2019-01-25 18:03:05 +03:00
**In conclusion, `ants` can up to 2x~6x faster than goroutines without a pool and the memory consumption is reduced by 10 to 20 times.**
2018-06-28 05:52:20 +03:00
2019-01-25 16:30:46 +03:00
[1]: https://travis-ci.com/panjf2000/ants.svg?branch=master
2018-06-29 05:45:58 +03:00
[2]: https://travis-ci.com/panjf2000/ants
2019-01-25 16:30:46 +03:00
[3]: https://codecov.io/gh/panjf2000/ants/branch/master/graph/badge.svg
2018-07-15 17:49:47 +03:00
[4]: https://codecov.io/gh/panjf2000/ants
2018-06-29 05:45:58 +03:00
[5]: https://goreportcard.com/badge/github.com/panjf2000/ants
[6]: https://goreportcard.com/report/github.com/panjf2000/ants
2018-07-15 17:45:55 +03:00
[7]: https://godoc.org/github.com/panjf2000/ants?status.svg
[8]: https://godoc.org/github.com/panjf2000/ants
[9]: https://badges.frapsoft.com/os/mit/mit.svg?v=103
[10]: https://opensource.org/licenses/mit-license.php