Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You are scratching at the surface of massively parallel programming. You need to think in a <a href="http://www.sics.se/~joe/index.html" rel="nofollow noreferrer">concurrency oriented way</a>. You are starting 51 Jobs, and not not the 50 jobs that you need to batch. The extra job is the one that manages the 50 jobs. In terms of the primitives required you need.</p> <pre><code>JOBHANDLE X= GetJobId(); //single job AddJob(JOBHANLDE X,ChildJob y); //container of jobs AddJobs(JOBHANDLE x, ChildJobs Y); BeginAsyncExecute(JOBHANDLE X); WaitTillResult(JOBHANDLE X); </code></pre> <p>You need an engine in the background that defines blocking primitives (beyond those provided by an OS kernel) and that manages worker threads and jobs to execute, which from the looks of it is handled by the PLINQ technology. PLINQ also uses green threads which is good.</p> <p>You have mentioned you will have a mix of databases and web-servers. Therefore your Job process/function will have to map the children to the correct resources before the batch is executed. 50 Children might therefore be reduced to far fewer batch-able RPC calls.</p> <p>So you build up your Job batch and then you block on it. </p> <p>Getting more specific will be hard. but in light of the discussion so far please tell me what you are having troubles with.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to make batch remote calls to database or service?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USHassan Syed
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI like this method having seen a similar solution in a project I have worked on. I think this will also give you flexibility in future if you have to change how/what you want to do before/during the remote call
      singulars
      1. PO
      1. USAmit Wadhwa
    2. COHi Hassan, Thanks for your insights! I have to apologize in advance that i'm very busy with other stuff so can't give this dicussion my fullest attention. The blocking primitives are what i'm looking for i think, although there is another issue that Richj helped me to. I have a tree of objects and then i have expression trees on those. My idea for fast runtime code was to have the expression trees compiled to native code. This however leads to a problem because then execution of the expression trees will always be depth firstunless i rewrite the code.
      singulars
      1. PO
      1. USgjvdkamp
    3. COI think Futures might actually be a good place to start my search, because they allow for parallization before the actual return value is used, the work needs to be exposed to the framework before the result is required. Also they smell like the 'blocking primitive beyond the OS' you mention. So ServiceCallX() + ServiceCallY() would become something like. Future<double) X {ServiceCallX}; Future<double> X {ServiceCallY}; X + Y; This nicely breaks up all the calls to the remote services into seperate bits, nice. But now how do I cluster them into batches share the overhead of remote calls?
      singulars
      1. PO
      1. USgjvdkamp
 

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