What’s missing from your sketchup is how the two threads are intended to work together. Do they work “together,” e.g. one is capturing data that the other one is producing? That’s going to make a tremendous difference in how the whole thing should be properly set-up.
But in any case ... threads shouldn’t have tight timing-expectations like you describe. If a thread is consuming something, let it read from a queue (e.g. Thread::Queue), simply blocking on the read if there is nothing there to read yet. Ditto, let a producer-thread push data onto such a queue and keep going on its merry way. If someone needs to monitor the status of something, push status-messages onto some queue for the monitor to remove. If it’s time to shut-down the child threads, send a “please shut down” command-message to that child’s queue.
Queues act like flexible, stretchy hoses, buffering away the timing dependencies and letting the threads run efficiently at full speed with little or no need to “rendezvous” with one another.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||