Hi All, Does the performance of the web application decrease when we deploy a 2 tier web application where the number of users are more(say 300+),Please advise?

Question

1.00/5 (1 vote)

See more:

, +

Hi All, we have developed a web application using 2 tier architecture since the number of users are less than 30, now we need to deploy the same application to another client where the number of users are more than 300, please advise, I think may be converting this 2 tier to N-tier may be a good idea, but still wants to know, whether i am right or wrong before moving ahead. and please also let me know, if there are any alternate to this or what is the best way of converting 2-tier to N-tier. Thanks in advance.

Posted 20-Aug-13 22:38pm

Prathap S V

Add a Solution

Comments

Thanks7872 21-Aug-13 5:17am

Don't write whole question in title.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Bala Selvanayagam · Answer 1 · 2013-08-20T22:54:00

Solution 1

I presume all your processing is done at server level(where the database is and the IIS hosting is) and the workstations are running the web client.

Converting this into an N- tier application may help your to distribute across several server - distributing the load and making it faster but all depends what is the processing power needed for those 300 users and how you are going to distribute and importantly how many concurrent users at a given time ?

It all down to your current architecture (which i do not know), how does it performs at the current 30 user load and the prediction for the 300 users and the plan for distributing.

Converting your application into n-tier may be a time and money consuming exercise.

One this you could look into this the option hosting in the cloud and you can configure your hosting account that if the server becomes busier (the application is slower) automatically increase the processing power - in other words your hosing account will automatically add more processing power when it needs more resources and when you do not need it will be back on your normal resource requirement.

Posted 20-Aug-13 22:54pm

Bala Selvanayagam

Comments

Prathap S V 21-Aug-13 7:00am

@ Bala Selvanayagam, thanks for the answer, yes what you have assumed is correct, but when it comes to application performance, if the code written to built the application is of good quality with a good system design then, will it(my current 2-tier application) support when the no. of users are more.?
also you said "N- tier application may help your to distribute across several server", i see all the layers[business logic,business entity and data access layer] usually lies in the same application folder most of the times in N-tier or 3 tier architecture..

Bala Selvanayagam 21-Aug-13 7:54am

It all depends how you have architecture your application. My understanding is that your web form (my assumption) is directly talking to your database using ADO ? alternatively, you could separate data access layer on a different server. To be honest, unless you explain how is your current architecture is, it is difficult for me to go on....

The performance depends on

1.The database table normalization and whether you use TSQL /Stored procedure

2.The database is properly indexed & optimized ?

3.You have used minimum run time logic in your web form ?

4.Are you doing many round trips to the server ?

5.Your current experience with 30 users, what is your current server specification and how does the server perform now. This could be a bench mark for you to estimate 300. You needs to know how many users out of 300 is going to use the system at the same time ? Based on these you could size the server (how many CPU/CORE, Mormoy and IO )

6. Also you could think about using multiple IIS server, this means you could use two IIS server and part of the use base is routed through one server and the rest is through the other (the URLs could be different for them - load balance) but evenually talking to the same server