ThreadLimiter forks threads like Thread.fork(), but limits the number of concurrently running threads.
ThreadLimiter isn't a thread pool. Each fork really starts a new thread.
Example: Get the titles of a large collections of URL's.
The traditional way, using Thread directly:
urls = [.....] # A lot of URL's. Maybe even thousends.
titles = urls.collect do |url| Thread.fork do # ...get the title of the url... end end.collect do |thread| thread.value end
With ThreadLimiter#fork():
require "threadlimiter"
urls = [.....] # A lot of URL's. Maybe even thousends. thread_limiter = ThreadLimiter.new(10) # Max. 10 concurrently running threads.
titles = urls.collect do |url| thread_limiter.fork do # ...get the title of the url... end end.collect do |thread| thread.value end
With Enumerable#threaded_collect():
require "threadlimiter"
urls = [.....] # A lot of URL's. Maybe even thousends.
titles = urls.threaded_collect(10) do |url| # Max. 10 concurrently running threads. # ...get the title of the url... end
FAQs
Unknown package
We found that threadlimiter demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
Security News
A clarification on our recent research investigating 60 malicious Ruby gems.
