Re: Memory Manager Tests - using 512 Threads

Danijel Tkalcec [RTC] wrote:
> "David J Taylor" wrote:
>> Pardon me for asking a silly question:
>>
>> - if you get more throughput with less memory using 16 threads, why
>> would you want to consider even using 512 threads? Does this
>> suggest that somewhere between 1 and 512 threads there is an optimum
>> value?
>
> In this test, Clients are virtualy flooding the Server with requests,
> so that most Threads are occupied full-time. In a normal productive
> environment, even if you allow RTC to use 512 Threads, it will most
> likely have less than 20 Threads working at the same time. And since
> Thread pool in RTC is growing on-demand, threads won't even be
> created if there is no work to do for them.
>
> Having the abbility to work with more Threads at the same time is
> interesting for Servers which have to process a number of long-running
> requests. When there are free Threads available in the pool,
> long-running requests won't block the rest of the communication.
>
> So, the decision is simple:
> "How many parallel threads do you want to allow at peak times"?
>
> I've set up the Default value to 256, which is what most Web Servers
> use.

So you are saying that, under normal use, having the extra inactive
threads available ready for an I/O completion is a benefit?

David


.

Relevant Pages

  • Re: Memory Manager Tests - using 512 Threads
    ... In this test, Clients are virtualy flooding the Server with requests, so ... And since Thread pool in ... When there are free Threads available in the pool, long-running ... I've set up the Default value to 256, which is what most Web Servers use. ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Async Pages and Thread Pools
    ... Microsoft MSDN Online Support Lead ... concurrent requests exceeds the number of available request-processing ... threads in the thread pool. ...
    (microsoft.public.dotnet.framework)
  • Re: apache httpd performance
    ... Both servers share same dns server, so I do not think that the DNS can be issue. ... We'd be better off ignoring the Linux results entirely and simply try instead to optimize your FreeBSD performance. ... My big surprise was that CPU: AMD Athlon64 Processor 3200+ can't handle 100 concurrent requests normally e.g. the load on the servers goes very high, and the server does not respond very well during the test. ...
    (freebsd-performance)
  • Re: Using external IP/DNS name for accessing internal resources
    ... Is 100.100.100.100 an IP owned by ISA (used for publishing ... When the proxy relays the requests to other servers, ...
    (microsoft.public.isa.publishing)
  • Re: What is this?
    ... >This event is generated when TCP traffic to port 0 is detected. ... This fails on a properly set up firewall. ... accessible DNS servers - one in the DMZ, and two located at our upstream. ... All internal DNS requests go to servers behind the firewall, ...
    (comp.security.firewalls)