网站变慢 重启apache后通常
网站变慢 重启apache后正常
网站变慢 重启apache后正常,重启后一段时间又变慢了,服务器cpu和内存都正常,而且用的都很少的,ping反应也快,一般10多ms,不过就是出现打开网站慢的情况,最近出现的,请问大牛们应该这个排查,额,不要回答就说查apache日志哈,最好说哈应该咋个查,估计是那种情况出现的问题,如果出现了在日志里表现是怎么样的.....
------解决方案--------------------
其实我也遇到过,过了一阵自己就好了,至今原因未知。
------解决方案--------------------
关键就在于 用的都很少的
由于用的很少,所以 apache 所需的内存被挤到硬盘上去了,甚至所需的动态链接库都被从内存中卸载了
等到用的时候再从硬盘中加载,甚至还要加载动态链接库。那当然就慢啦
------解决方案--------------------
重启apache后正常
原因根本就是apache
重新安装后,试一试。
------解决方案--------------------
老大这个解释似乎不妥啊,如果是你说的这个原因,那只要用浏览器访问几次,应该就能恢复正常了,楼主恐怕也就不会提这个问题了。
------解决方案--------------------
优化一下参数试试。。
------解决方案--------------------
可能服务器问题吧,
------解决方案--------------------
清清缓存试试
------解决方案--------------------
apache的连接数怎么样? 带宽够用吧
------解决方案--------------------
首先确定是apache问题,会不会是解析url变慢了,重启一下机器能不能好点呢
------解决方案--------------------
重启后一切都正常,表明apache什么的都没问题, 过段时间就变慢了,,这下问题就出现了,,,你在慢慢排查吧,,,
这问题表示很蛋疼...
------解决方案--------------------
win还是linux?
------解决方案--------------------
确实挺蛋疼的...
------解决方案--------------------
------解决方案--------------------
是不是跟程序有关? 程序写得不好也会让apache很累的。。。即使访问量比较少
------解决方案--------------------
http://www.blogjava.net/itvincent/archive/2009/12/11/305522.html
------解决方案--------------------
电脑的原因吧……

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











To set up a CGI directory in Apache, you need to perform the following steps: Create a CGI directory such as "cgi-bin", and grant Apache write permissions. Add the "ScriptAlias" directive block in the Apache configuration file to map the CGI directory to the "/cgi-bin" URL. Restart Apache.

There are 3 ways to view the version on the Apache server: via the command line (apachectl -v or apache2ctl -v), check the server status page (http://<server IP or domain name>/server-status), or view the Apache configuration file (ServerVersion: Apache/<version number>).

Apache connects to a database requires the following steps: Install the database driver. Configure the web.xml file to create a connection pool. Create a JDBC data source and specify the connection settings. Use the JDBC API to access the database from Java code, including getting connections, creating statements, binding parameters, executing queries or updates, and processing results.

When the Apache 80 port is occupied, the solution is as follows: find out the process that occupies the port and close it. Check the firewall settings to make sure Apache is not blocked. If the above method does not work, please reconfigure Apache to use a different port. Restart the Apache service.

How to view the Apache version? Start the Apache server: Use sudo service apache2 start to start the server. View version number: Use one of the following methods to view version: Command line: Run the apache2 -v command. Server Status Page: Access the default port of the Apache server (usually 80) in a web browser, and the version information is displayed at the bottom of the page.

How to configure Zend in Apache? The steps to configure Zend Framework in an Apache Web Server are as follows: Install Zend Framework and extract it into the Web Server directory. Create a .htaccess file. Create the Zend application directory and add the index.php file. Configure the Zend application (application.ini). Restart the Apache Web server.

Apache cannot start because the following reasons may be: Configuration file syntax error. Conflict with other application ports. Permissions issue. Out of memory. Process deadlock. Daemon failure. SELinux permissions issues. Firewall problem. Software conflict.

To delete an extra ServerName directive from Apache, you can take the following steps: Identify and delete the extra ServerName directive. Restart Apache to make the changes take effect. Check the configuration file to verify changes. Test the server to make sure the problem is resolved.
