To briefly introduce, some of his own problems, this week work is trying to identify the company's web side management system is not stable, and then I login jump server found server memory occupied by more than 80%, in the open service is overmuch, big probability is caused by the problem, now require is in still other service situation, let I need to search the web project for stable==I think the best thing to do is, spending money to add memory, don't know what people have good advice, such as delete nginx log files, such as feeling a drop in the ocean

CodePudding user response:

Isn't just a web server, you can have multiple instances of shunt, or to limit flow can also add memory can't solve the problem of nature,

CodePudding user response:

Still trying to identify the thread, memory access to relevant information, through optimizing the code to solve,

CodePudding user response:

reference 1st floor KeepSayingNo response:

isn't just a web server, you can have multiple instances of shunt, or to limit flow can also add memory can't solve the problem of essence,

A lot of a web server, just let me see the server project deployment is overmuch, memory footprint is too big, and then apply for expansion today already

CodePudding user response:

refer to the second floor DayDayUp, reply:

or the thread of the February, memory information, by optimizing the code to solve,

The link operation related to learning? Novice, stiff operation, mainly is your server, did not dare to play blind