This post originated from an RSS feed registered with Java Buzz
by Brian McCallister.
Original Post: Why drbunix:// is Cool
Feed Title: Waste of Time
Feed URL: http://kasparov.skife.org/blog/index.rss
Feed Description: A simple waste of time and weblog experiment
So, ruby threads have issues. Multiprocessing, on the other hand,
works great. I have been doing stuff like:
#!/usr/bin/env ruby
require 'drb'
URI = "drbunix:///tmp/foopie"
class Master
def initialize(count=100)
@jobs = []
count.times do |i|
@jobs << "Job ##{i}"
end
end
def take(n)
taken = []
while taken.length < n && !@jobs.empty?
taken << @jobs.shift
end
taken
end
end
DRb.start_service URI, Master.new
pids = []
10.times do |i|
pids << fork do
DRb.start_service
master = DRbObject.new_with_uri URI
until (jobs = master.take(2)).empty?
jobs.each do |j|
puts j
sleep rand
end
end
end
end
puts "started children"
pids.each { |pid| Process.wait(pid) }
To slam though jobs in ruby. Doing it over
unix sockets instead of tcp is just nicer =) It just spreads the
workload across processes instead of threads.
Previous Topic
