Using concurrent extensions in web applications

I would like to hear some opinions about the role, if any, of parallel computing approaches, including the potential use of parallel extensions ( June CTP for example, ), have in web applications. In what scenarios is this approach suitable and / or not suitable?

My understanding of how accurately the tasks of IIS threads and web browsers is quite limited. I would appreciate understanding if someone out there understands it well. I'm more curious to find out if IIS and web browsers limit the ROI of creating multi-threaded and / or asynchronous tasks in web applications in general.

Thanks in advance.

+5
source share
5 answers

Well, web servers present an interesting problem, since they already have multithreading, serving concurrent requests. Thus, at a busy place, you cannot rely on the possibility of stealing a large number of cores for your purposes. Of course, if you expect only light traffic, and your site requires a lot of crunches (data processing, etc.), you can get some savings.

I would expect Parallel Extensions to work better on the client or specialized service applications where you can reasonably expect the kernels to be available for your use [ab].

+3
source

-. ( db -), , .

- . . (dbms -) , , , .

, , db webservice , httpcontext . ajax .

0

, , PE, . Microsoft IIS.

, , , -, . PE .

, - . PE -, 20 , , - -. ( , , , ). , , , 5 30 , /PE.

- , . , , . PE .

0

, TPL -, . , - . , , 100%, parallelism .

:

.NET 4 ASP.NET

0

-, , , . ( ).

: , IIS . , " " -. - , , .

, . IIS ? . ? .

-3

All Articles