Webserver does not work with large numbers of users

[agustinh2000]

Hi, I have a problem with the webserver.
When a large number of users working on the webserver system stops working and you have to restart.

Any Idea?

Agustín

[Bruce]

thousands of ideas.

But perhaps first define what a "large number" is, and also what NetTalk version you are using.
And maybe something about the app - what database you are using and so on.

cheers
Bruce

[agustinh2000]

* 100 users per server
* NT 8.28
* We use Database: MSSQL and MySQL
* They network lan and internet
* Windows 2008 server.

Anything else?

[osquiabro]

i have 1400 user per server  with MSSQL and Windows 2008 server, without problem, 3 years running.

[agustinh2000]

100 users per server access (approximately)

[Keith]

Hi Agustin

The number of users you can support on a web server depends primarily on:

• The capacity of the server (CPUs, Ram, network speed)
• The number of user transactions per second
• The processing that occurs per transaction
• Processing from other applications on the server

If you have a small capacity server, a large number of users and a heavy per transaction processing load then you might get slow response times and ultimately some bad things may happen to your application.  So these factors need to be in balance.

However, with only 100 users you are unlikely to get any more than 10 transactions per second  and if your code is executing an average number of instructions then there should be no problem on a dedicated web server.

I have a NetTalk app which calculates 34,000 values for every 'transaction' and have estimated that, based on a maximum transaction rate the server (8 cores, 8 threads) can support 700 concurrent users.

I think that if your server 'stops working' (and you need to define what that means before you can effectively trouble shoot) it is likely that the problem is somewhere in the code - or one of the other factors noted above.

Cheers

Keith

[kevin plummer]

Hi Agustin,

I don't think the number of users is the problem.

I think you have probably got a transaction lock on SQL. If you kill your web app this then frees the lock and it works again until another lock. You can run a query in SQL to show you any locked process's to confirm if this is the case when your app stops working. To fix the problem make sure you use SQLTimeout around your file access code.

Check you also have set MARS and Busy handling. These are unrelated to your problem but you will have other undesirable side effects if you don't set.

Search this NG for more info on SQLTimeout.

Cheers,

Kev

[agustinh2000]

I'll try.
thank you very much