Here's a variation of the clone method where I slice the dataset up into 4 chunks and imported each within its own thread. The first run I did worked and executed in about 7.5 minutes vs. the 9 minutes of the single thread approach, but the 2nd, 3rd, 4th runs I attempted never quite got off the ground with only the 3rd run actually cloning about 2500 records while the others cloned zero. I thought maybe my attempt to update the progressbar from each of the threads was a problem, so I commented the pbar lines altogether to no good effect.
http://gist.github.com/377437 Isn't one of the hypes of JRuby its "true threading" model? Or am I misunderstanding that claim altogether in my attempt to utilize the Thread class to divide and conquer as I did here? I'm totally baffled because the first run actually ran and worked! The statistics in the jconsole were not appreciably different than previously reported. Charles, your post came in as I wrote this. I'll give the benchmark page a read and the server mode a go and see what I churn out with the original approach on Monday when I'm back in the office. Michael -- http://codeconnoisseur.org -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
