Obviously, the first order of business (after determining that the interface that you are using is, in fact, thread-safe), is to determine that implementing this process using multiple threads actually will be faster. The only thing that multi-threading can realistically do is to overlap computation with I/O, and, to a certain but limited extent, to allow multiple I/O requests to be serviced in parallel. Everything, in your scenario, will depend upon the implementation capabilities of the Win32 subsystem with which you are ultimately communicating. If you, as you say, “know nothing about threads,” why do you have reason to believe that threads will actually help you? (I mean that as a perfectly serious question.)
Another often-overlooked strategy is simply to run multiple instances of the same Perl program on the same computer at the same time, arranging by some means for each of them to be issuing a different set of requests. Thus, with no added internal complexity to any one of the systems at all, as many copies as desired “of the whole thing” can be run in parallel.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||