Click here to Skip to main content
14,775,008 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
Hi All,

I am currently developing TCP/IP application using .net platform. i got some concern that my application will be used a lot of users, may be a million user at the same time, so i scare that will my application handle for it ? is there any suggestion for this kind of scenario because i never come across before.

Which is the best way to do it? if possible, please provide some samples thanks.

Best Rgds,
Be brave... :-)

(I'm afraid this post lacks matter, as you share too little detail. How can we know anything about its performance?)

Mike Meinz 7-Sep-13 10:11am
Design your application so that it can be distributed to run on multiple servers. As demand increases, you can bring additional servers online. You will need to design caching mechanisms to have data that is frequently accessed but seldom changed available quickly and some way to refresh or age the cache to keep it up-to-date. ,

1 solution

Considering you haven't described anything at all about what type of application your talking about (Windows Forms, ASP.NET, WPF), what your application does, where it runs, if there is client and server sides to it, if it uses some database, what database engine that is, capacity information on what the amount of information clients can generate, what the server (if any) expects to handle, ..., absolutely NOTHING AT ALL about it!

For all we know you've made a copy of Notepad and a million people using that all at the same time means absolutely nothing since not a single instance of your application knows anything about a server or any other copy of the app running anyway in the world!

It's impossible to answer your question.
dartfrog 7-Sep-13 12:48pm
Hi Dave, my application is console app running on windows server 2008 r2 and developed with my application accepts XML file from clients. as soon as application received XML file, it will save inside MS SQL 2008 database. Moreover, my Server is dedicated server.
Dave Kreskowiak 7-Sep-13 22:03pm
OK, that scratches the surface, but is still not enough information. How big are these XML files? Does the server have to do any processing of these files? How often does each client transfer these files? How are the files uploaded? What protocol is being used? FTP? HTTP? Some "Roll you own transport" protocol? How many simultaneous clients are you talking about? Does each file have to be processed at the time it's uploaded or can it wait a certain amount of time before being processed (queued up work)?? Does each client need to have some kind of response sent back to it and what are the details of that response? How big are the replies? When are the replies expected? Does the traffic load rise and fall during the day? Week? This is a dynamic load. Can you look into possible cloud hosting and automatic load distribution? ...? ...? ...?

Getting the idea yet?? You MUST take all the tiny details into account. This will not only dictate the load on the server but also on the scalability of your server-side application.
dartfrog 11-Sep-13 22:50pm
Hi Dave, XML file is about 40kb. my tcp/ip application will accept all incoming xml files (may be one or more than one) from multiple clients (may be same time or simultaneously) and convert it to image file. after receiving xml file, send "OK" to client(s). may be 100,000 clients is using but i hope 1000 clients can get simultaneous condition.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900