Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have implemented a reverse proxy through an Async Http Handler for benchmarking purposes (as a part of my Phd. Thesis) and run into the very same problems as you.</p> <p>In order to scale it is mandatory to have processModel set to false and fine tune the thread pools. I have found that, contrary to what the documentation regarding processModel defaults says, many of the thread pools are not properly configured when processModel is set to true. The maxConnection setting it is also important as it limits your scalability if the limit is set too low. See <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;821268" rel="nofollow">http://support.microsoft.com/default.aspx?scid=kb;en-us;821268</a></p> <p>Regarding your app running out of ports because of the TIME_WAIT delay on the socket, I have also faced the same problem because I was injecting traffic from a limited set of machines with more than 64k requests in 240 seconds. I lowered the TIME_WAIT to 30 seconds without any problems.</p> <p>I also mistakenly reused a proxy object to a Web Services endpoint in several threads. Although the proxy doesn't have any state, I found that the GC had a lot of problems collecting the memory associated with its internal buffers (String [] instances) and that caused my app to run out of memory.</p> <p>Some interesting performance counters that you should monitor are the ones related to Queued requests, requests in execution and request time under the ASP.NET apps category. If you see queued requests or that the execution time is low but the clients see long request times, then you have some sort of contention in your server. Also monitor counters under the LocksAndThreads category looking for contention.</p>
    singulars
    1. This table or related slice is empty.
    1. POScalability issue when using outgoing asynchronous web requests on IIS 7.5
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UStrigoesrodrigo
    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
    1. COThanks for you comment. I am not able to write a long answer in a comment, so I will add some comments higlighted in your text instead. Please feel free to comment on these in the same manner. Much obliged for your input.
      singulars
      1. PO
      1. USToby999
    2. COFor some reason, my updates in your comment was removed. :( Either by you or someone else manually or by StackTrace automically. Either way, I guess it is not the preferrable way to give reponse to a answer and the comments here don't allow enough space to give a proper response. A bit tiring since it took some time to write down the answers (I sa the post was successful on the page) in your comment. I'll ponder a bit on of how to give this feedback..
      singulars
      1. PO
      1. USToby999
    3. COThank you, I was also curious why I wasn't seeing any comments. Fine tuning ASP.Net applications to scale is a hard topic and I am eager to learn from the experiences of other people.
      singulars
      1. PO
      1. UStrigoesrodrigo
 

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