Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POHow to determine optimal number of threads for high latency network requests?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USsoru
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThat's flat-out incorrect in this case. If I run with a single thread, and assuming a 3-second turnaround for each request (they average about 3, with a standard deviation of about 1 second), making 65,000 requests will take approximately 54 *hours*. Running my program with 1024 threads takes about 20 minutes. Less is absolutely *not* better in the described conditions.
      singulars
      1. PO
      1. USseawolf
    2. COI'll rephrase that to say that answer is *misleading*. I have a provable case where increasing the number of threads radically reduces overall job completion time. A different approach would be using asynchronous IO, which (if I understand correctly) can have similar or greater performance impact. In terms of simplicity, however, threads are quicker to get up and running, and in many cases are appropriate for jobs of this type but smaller scale.
      singulars
      1. PO
      1. USseawolf
    3. COOK, I'm humble enough that I can say I misunderstood your post and agree with what you are getting at. In the future it would help if you included an example of a replacement strategy. As pointed out in [this reply](http://stackoverflow.com/a/19565450/1886109), Actors are conceptually lightweight threads and if I can use that or some similar concurrency model then I agree, true threads are overkill. "Conceptually" is the key word here, I need some sort of concurrency, and threads are one reasonable way to achieve that, just not at the scale that I need.
      singulars
      1. PO
      1. USseawolf
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload