Package ants implements a fixed goroutine pool for managing and recycling a massive number of goroutines, allowing developers to limit the number of goroutines that created by your concurrent programs.
## Features:
- Automatically managing and recycling a massive number of goroutines
- Friendlyinterfaces: submitting tasks, getting the number of running goroutines, readjusting capacity of pool dynamically, closing pool
- Efficientinmemoryusage and it even achieveshigher performancethan unlimited goroutines in golang
## How to install
``` sh
go get -u github.com/panjf2000/ants
```
Or, using glide:
``` sh
glide get github.com/panjf2000/ants
```
## How to use
If your program will generate a massive number of goroutines and you don't want them to consume avastamountofmemory, with ants, all you need to do is to import ants package and submit all your tasks to the default limited pool created when ants was imported:
``` go
package main
import (
"fmt"
"github.com/panjf2000/ants"
"sync"
)
func myFunc() {
fmt.Println("Hello World!")
}
func main() {
runTimes := 10000
var wg sync.WaitGroup
// submit all your tasks to ants pool
for i := 0; i <runTimes;i++{
wg.Add(1)
ants.Push(func() {
myFunc()
wg.Done()
})
}
wg.Wait()
fmt.Println("finish all tasks!")
}
```
And ants also supports the custom limited pool. You can use the `NewPool` method to generate a pool with the given capacity, as following:
``` go
// set 10000 the size of goroutine pool
p, _ := ants.NewPool(10000)
```
## Readjusting pool capacity
You can change ants pool capacity at any time with `ReSize(int)`:
``` go
pool.ReSize(1000) // Readjust its capacity to 1000
pool.ReSize(100000) // Readjust its capacity to 100000
```
Don't worry about the synchronous problems in this case, this method is thread-safe.
## About sequence
All the tasks submitted to ants pool will not be guaranteed to be processed in order, because those tasks distribute among a series of concurrent workers, thus those tasks are processed concurrently.
In that benchmark-picture, the first and second benchmarks performed test with 100w tasks and the rest of benchmarks performed test with 1000w tasks, both unlimited goroutines and ants pool, and the capacity of this ants goroutine-pool was limited to 5w.
