How to handle 100000 users request with sql server which not decrease sql server performance? please guide me here.
asked
How to handle 100000 users request with sql server which not decrease sql server performance? please guide me here.
Is that 100,000 active queries, or 100,000 simultaneously-connected users doing their thing so not necessarily hammering the snot out of the server?
The obvious is to throw hardware at the problem, so:
- CPUs. Lot of 'em, as fast as possible
- Memory. Lots of it, ditto
- Disks. The fastest possible, as near to the server as possible
- Network. The fastest possible, and lots of it.
- Read-only stuff? Get that off that primary server and put it on a readable secondary
However, no amount of hardware is going to fix a badly-written application running against a badly-designed, inadequately-indexed database.
actually users like on e shoping cart, cricket score application like all that who fetch data from database at same time like cricket score.
Live cricket scores? They're not so fast-moving that you can't get away with some decent caching algorithms. Historical scores can be offloaded onto a server away from the updating stuff.
e-shopping, though, that needs to be carefully designed, particularly if you're doing stock-checking at the same time.
18 People are following this question.
