Databases
StackOverflow2013
Usersdbo
USseawolf
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USseawolf
    primarykey
    data
    text
    plurals
    1. PODynamically-built LINQ query gives inconsistent results depending on how it's built
      singulars
      1. PTQuestion
    1. PODynamically-built LINQ query gives inconsistent results depending on how it's built
      singulars
      1. PTQuestion
    2. POHadoop giving SCDynamicStore on my JAR but not on hadoop-examples.jar
      singulars
      1. PTQuestion
    3. POHow to match images with unknown rotation differences
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. COI see that you say there are millions of files, but they are probably not all in one directory. If the number of directories you are moving files to is large compared to the number of files (probably something like 1:5, but you would have to profile to find the right number) then you just want to use the first technique. If the number of directories is small and the number of files you are copying is large, that single transfer of the names of all files in each of the directories you care about is small compared to the number of round trips you have to make if you try to copy each file.
      singulars
      1. PO
      1. USseawolf
    2. 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
    3. 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
 

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