Closed bmhatfield closed 9 years ago
I moved this script to a Linux machine where it's a bit easier to tune maxprocs... and it just creates ruby threads indefinitely. I finally killed it with hundreds and hundreds of threads and a completely pegged CPU.
Based upon my script, I would not expect it to be using a new thread for every request, but to just re-use the existing threads. What am I doing wrong here? What workarounds exist for this?
PS: I tried setting pool_size in the client constructor, but it seemed to have no effect.
OH NO! I just noticed that I was instantiating a Ridley client on every iteration. Very embarrassing. So sorry for filing this issue for my own foolishness.
@bmhatfield no problem! Glad you were able to solve your problem
Hi,
I have a short script like this:
This runs for a while (exactly 70
Found node
lines are printed) before a fairly large stacktrace is printed:I am unfortunately not sure how to proceed here. I don't know very much about celluloid, or why it's exploding. I'm on OSX, if that matters.