Question 1

How do I use Tunny to limit concurrent HTTP request processing in Go?

Accepted Answer

Create a pool with tunny.NewFunc matching CPU count, then call pool.Process in your HTTP handler to block until job completion, as shown in the README example. For timeouts, use ProcessTimed or ProcessCtx with context from requests.

Question 2

Tunny vs native Go goroutines: which is better for my project?

Accepted Answer

Use Tunny when you need to limit parallel execution, such as for CPU-bound tasks or resource throttling. Native goroutines are sufficient for simple concurrency without pooling, but Tunny adds control over parallelism with a synchronous API.

Question 3

Does Tunny support job cancellation and deadlines?

Accepted Answer

Yes, Tunny integrates with Go's context package through ProcessCtx for cancellation and deadlines. You can also use ProcessTimed for simple timeouts, making it flexible for handling job expiration.

Question 4

How to handle errors in Tunny worker functions?

Accepted Answer

Error handling is developer-defined; the worker function should return errors as part of the interface, and Process methods return errors for timeouts. For custom errors, implement logic within the worker or use context cancellation.

Question 5

What's the best way to determine pool size in Tunny?

Accepted Answer

For CPU-intensive tasks, set pool size to runtime.NumCPU() as recommended in the README. For I/O bound tasks, adjust based on system resources and workload, using SetSize for dynamic changes during runtime.

Question 6

Can I use Tunny for I/O bound operations or is it only for CPU intensive work?

Accepted Answer

Tunny can be used for I/O bound tasks, but its fixed pool model is optimized for CPU parallelism. For I/O, you might need a larger pool size or consider other strategies, though the synchronous API still applies for coordination.

Question 7

How to implement a custom worker with persistent state in Tunny?

Accepted Answer

Implement the tunny.Worker interface with Process, Interrupt, and Terminate methods, then use tunny.New with a constructor function that returns your custom worker, managing state per goroutine as described in the README.

tunny

What is tunny?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions