Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Question 1: What all is running on this box? If I read correctly, you have one site with 50,000 products (no mention of users or hits) and another with lots more. As you stack sites, you will see some degredation, even if your code is very tight.</p> <p>Question 2: Do you have all layers on a single box? You now have competing concerns and might block some CPU bound threads due to I/O operations.</p> <p>Question 3: Have you code reviewed to ensure proper development concepts and methodologies (SOLID, etc)? If not, you could hold resources longer than needed and cause issues.</p> <p>Question 4: Have you profiled? I mean both SQL Server and the web application. if not, you have no clue where the issue might be and I doubt anyone can help you in this forum.</p> <p>Even with millions of "products", a properly designed database and site should be fairly fast. But, different factors come together to represent performance. All of the pieces on all layers can affect the application. </p> <p>As an example, I consulted once on a company that had built a high performance eCommerce application that was dying. All of the parts seemed fine in code reviews. In tests, both the pages and the database worked fine. But they had never stressed the system. If they had they would have caught this little bit of insanity.</p> <pre><code> //let's not focus on the magic string, okay? Think about static private static SqlConnection connection = new SqlConnection("{conn string here}"); </code></pre> <p>The entire site was filtering through a single SQL Connection because one developer did not understand the concept of the underlying connection pool and thought object initialization would be more of a hit than filtering through a static "always on" connection.</p> <p>Until you profile the application, you don't have a question here that can be answered. Once you find an issue and ask, someone can step up and say "here is how you solve that". You can add more information to this question, but until there is a problem identified, rather than a generic symptom, you are going nowhere.</p>
    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.
 

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