C # client service procedures, at the same time, start multiple threads concurrent access IIS sites on the web service interface, resulting in IIS on site to collapse, what's the solution

CodePudding user response:

Iis limit under concurrent
https://www.cnblogs.com/vettel0329/p/11052991.html
Optimize the server code
Access speed, the client under the limit,

CodePudding user response:

Just need to learn

CodePudding user response:

Concurrency is too big, become attacked,

CodePudding user response:

Current limit, more than traffic will return an error

CodePudding user response:

The site is too rubbish, complaints

CodePudding user response:

1. Limit the concurrency value;
2. Optimize the processing logic, reduce the processing time, put the logic to another thread;
3. The server performance;

CodePudding user response:

IIS site on the web service interface, this is the third party or write their own? Why will collapse?
Or not for optimization and attack? Ruled out the problem first,

If several concurrent collapse slightly off, the webservice is supposed to be unqualified,

CodePudding user response:

Might as well take a look at the service method in the code, and see what all the operation

CodePudding user response:

Server can't get 10 128 gg virtual machine to run the webservice then use 10 ng agent this IP.


The IIS application pool queue set 65535, the biggest set 65535 you still don't think its working process