Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. This table or related slice is empty.
    1. COThanks for input. As for maxconnection I think this is regulated by the autoConfig=true which should mean the max value is set to 12 * #CPUs. I think this config is the same as set by the System.Net.ServicePointManager.DefaultConnectionLimit programatically (I'll update the text above on this). But in our case TCP connections are used for either 1) incoming requests from lots of individual IP address in which case no more than 1 connection should be needed (I think), or 2) outgoing TCP calls to several other servers. But all of these are using persisted connections. I.e. no more than 1 per IP.
      singulars
    2. COI'll (re)look into correctly disposing connections. We are actually having a lot of finalisers running on the server (as detectable in windows performance counter) which could indicate that there is a problem of objects not being disposed correctly. I'll update this info when I have analysed it. Regarding connection pooling I don't think this is a culprit since we only use tasks in the requests flow, thus the .NET ThreadPool. But maybe I misunderstand you?
      singulars
    3. COThe connection pooling suggestion applies if you have your own implementation of connection pooling.. Example: If you are making a WCF call to an internal service, you will be using a client object. This client object can be used in your own implementation of object pooling to improve the performance because you can reuse the underlying tcp connections as well. The downside is that the custom implementation should be airtight in terms of implementation and should not end up leaking the wcf-client objects.
      singulars
 

Querying!

 
Guidance

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