Re: Threads, Sockets and OSX
Tim Hamilton <[email protected]>
| Newsgroups | gmane.comp.lang.ruby.general |
|---|---|
| Message-ID | <CAM8WUS_YsWjFgFqYCry9E5K7iCxCiwRF+Pnw7zfsD=bxrDv_VA@mail.gmail.com> |
I’m new here and hopefully don’t send you down a rabbit hole. Are you confident it’s not a hardware or os issue? Can you verify or recreate issue by doing similar task with other code? Just a thought. Best Tim On Fri, Dec 7, 2018 at 3:53 AM Peter Hickman <[email protected]> wrote: > Well the test with 2.6preview3 went ahead. It was similar to the other > versions but had it's own issues. It would run 100% cpu for 20 seconds, 50% > cpu for 20 second, repeated 4 to 5 times and then, 100% cpu for 15 seconds, > 0% cpu for 25 seconds, repeated 4 to 5 times and then back to the start. > Overall the throughput had dropped and the end to end test took much longer > > I've tried to eliminate any other processes that could interfere with the > test on my mac but a mac is not something you have that level of control > over (like you do with linux) > > I have a few other things to try though > > Unsubscribe: <mailto:[email protected]?subject=unsubscribe> > <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk> > Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>