If you are going to multi-thread queries, also check that query processing actually does occur in parallel. This would not only mean that the queries are being effectively handled as separate streams, but also that the queries themselves are capable of executing without contention with one another .. transaction isolation and so-forth. And that it is actually faster, given what you are actually trying to do and actual conditions.
Lately, I have switched more-and-more to simple programs that can be run independently of one another, i.e. as entirely separate processes, launched for example through a batch or workload-processing system. With this approach, there is of course no concurrency-issue within the application that must be considered, and the workload manager can tune the situation very directly: just launch as many copies as you need. Naturally you have to have a reliable and not-too contentious way to parcel up the work.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|