Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6374415
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T01:29:08+00:00 2026-05-25T01:29:08+00:00

When improving database performance, What is the fastest way? should I go straight to

  • 0

When improving database performance, What is the fastest way?

should I go straight to my target (5000 users)?
Or should I go through artificial milestones – (for example – first 1000 users, only then 2500…)?

we have a performance problem. For the purpose of the question, suppose the only bottleneck is the Database and all other resources consume zero time.

Facts:

  • Database performance for 50 concurrent users is good
  • Database performance for more then 50 is not acceptable and by that I mean database requests takes too long. Instead of ~0.5 sec they usually take between ~2 and ~7 sec, and sometimes even ~30 sec
  • On about 70 users, the system stop working at all, most database requests takes more then ~30 sec
  • Database is implemented in SQL SERVER 2005\8

Requirement:
The application need to support 5000 concurrent users.

From my understanding, and please correct me if I’m wrong or there is something missing, the best practise for database performance improvement is:

  1. Define performance objective targets.
  2. Establish testing environment identical (as much as possible) to production environment
  3. Check if the performance targets is OK. if not do the following until performance targets is OK

    3.1 Improve performance (on at a time) by – server re-configuration, indexes improvements ,code improvements, database structure improvements and more, using trace and monitor tools such as – performance counters, SQL Server profiler, logs and more

    3.2 Test and analyse the affects of the change and accept or reject it

My question is:
Assuming that getting the system to work on anything else then 5000, say for example 1000, or even 2500 users Doesn’t provide any business value, What is the fastest way to get to 5000 users?

  1. Getting there directly?
  2. Or first get to smaller milestones?
    for example – first target 500 users, then 1000, then 2500 ….
  3. Something else??

Do I get any technical value from using milestones, that will eventually take me to 5000 users faster?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T01:29:08+00:00Added an answer on May 25, 2026 at 1:29 am

    Tuning up to 500 users, for example, can lead you to solutions that won’t be effective when you increase to 1000 users. Example: let’s imagine that you can tune cache for 500 users, perhaps you won’t have enought RAM to get a good result for 5,000.

    Go for your goal.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I need help with improving the performance of the following SQL query. The database
What are some DOs and DONTs for improving database performance using index? A DO
What's a common/best practice for database design when it comes to improving performance on
I've recently been tasked with improving a records database that consists of the following:
I have been tasked with improving the performance of a slow running process which
Any personal experience in overcoming web application performance hurdles? Any recommended strategies for improving
Having just read the first four chapters of Refactoring: Improving the Design of Existing
I'm currently working on improving my database to make room for growth. As it
I'm in the process of improving an open-source music database, which reads songs in
I've been looking into improving SQLite performance for my site, especially with regard to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.