Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your reasoning is correct. Async delegates use threads from the thread pool so they should be faster compared to manual thread creation. Be careful though with this in ASP.NET applications. Because you will be eating up worker threads that are normally used by ASP.NET to service requests and your application might very quickly run out of servicing capabilities.</p> <p>Async delegates are fine for CPU intensive tasks. For I/O intensive tasks (such as reading streams, database calls and web service calls) you should use the BeginXXX, EndXXX methods offered directly by the corresponding classes (Stream, SqlConnection, WebClient, ...). This way you are not using any threads at all during the lengthy I/O operation. You are using <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa365198%28v=vs.85%29.aspx">I/O Completion Ports</a> which is the best thing in terms of I/O bound tasks. It will be orders of magnitude more performant and resource cheap than any threads and pools of threads.</p> <p>So to summarize:</p> <ul> <li>For I/O intensive tasks use I/O Completion Ports. If the I/O intensive task is wrapped inside a poorly written library that doesn't offer this possibility use the TPL that was introduced in .NET 4.0.</li> <li>For CPU intensive tasks use the TPL that was introduced in .NET 4.0.</li> </ul> <p>And if you don't have .NET 4.0 use thread pool unless you are writing an ASP.NET application in which case you might resort to manual thread creation.</p> <p>In general it is good practice to start using <a href="http://msdn.microsoft.com/en-us/library/dd460717.aspx">TPL</a> and orient your methods as tasks so that you are ready for .NET 4.5 which introduces the async/await keywords.</p>
    singulars
    1. This table or related slice is empty.
    1. POAsynchronous delegates vs Threads
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDarin Dimitrov
    1. USDarin Dimitrov
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAsynchronous delegates vs Threads
      singulars
      1. PTQuestion
    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. CO@ Darin : Thanks for the reply.Here the case is Windows Application, i think purely CPU intensive tasks, what about Performance while spawning 1000 threads vs 1000 del.begininvoke() call
      singulars
      1. PO
      1. USC-va
    2. CO@MSK, definitely go with TPL in this case and if you are using an older version of .NET use the thread pool (ThreadPool, BackgroundWorker, Async delegates, ... => they will all end up at the ThreadPool anyway). Don't spawn threads manually in this situation.
      singulars
      1. PO
      1. USDarin Dimitrov
    3. CO@ Darin: And I dont need Fire and forget. Here i'm in need of a dedicated thread to dequeue (regardless of ThreadPool) and at the same time it is long running process.
      singulars
      1. PO
      1. USC-va
 

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