当前位置:论坛首页 > Linux面板 > 求助

新安装的面板内存占用高,内存还溢出,请高手支招

发表在 Linux面板2018-3-9 00:52 [复制链接] 12 4126

用的是阿里云的1h1g的vps,操作系统选的是centos7.4的64位版本,之前一直用lnmp很稳定,今天听说宝塔面板不错,想装一个试试,结果安装好以后建立网站,上传wordpress以后填入数据库账号密码点下一步,感觉就慢慢的,等了几分钟好了,进入面板一看内存占用90%左右,进网站随便点几下就卡死了,请问这个情况是什么问题?怎么解决??谢谢!
未命名.png
使用道具 举报 只看该作者 回复
发表于 2018-3-9 09:31:14 | 显示全部楼层
私信把信息发给我。我上去瞄一眼
使用道具 举报 回复 支持 反对
发表于 2018-3-9 11:05:11 | 显示全部楼层
估计没有做优化吧?

----------------------------------------------------------------------------------------------------
菜鸟团队技术博客点击联系
使用道具 举报 回复 支持 反对
发表于 2018-3-9 11:13:16 | 显示全部楼层
penn 发表于 2018-3-9 11:05
估计没有做优化吧?

-------------------------------------------------------------------------------- ...

猜测PHP 的开销太大了
使用道具 举报 回复 支持 反对
发表于 2018-3-9 11:28:07 | 显示全部楼层
liang2580 发表于 2018-3-9 11:13
猜测PHP 的开销太大了

跟mysql也有关系!
使用道具 举报 回复 支持 反对
发表于 2018-3-9 11:31:26 | 显示全部楼层
penn 发表于 2018-3-9 11:28
跟mysql也有关系!

没啥关系,CPU都没有高。不
使用道具 举报 回复 支持 反对
发表于 2018-3-9 11:36:14 | 显示全部楼层
liang2580 发表于 2018-3-9 11:31
没啥关系,CPU都没有高。不

wordpress数据库不太高效,临时表很多的!
Snipaste_2018-03-09_11-33-13.jpg
使用道具 举报 回复 支持 反对
发表于 2018-3-9 12:24:54 | 显示全部楼层
penn 发表于 2018-3-9 11:36
wordpress数据库不太高效,临时表很多的!

这个tmp_table_size原来是8,现在我调到128,内存占用还是没下来,78%,郁闷,老大还有哪里可以优化的??
使用道具 举报 回复 支持 反对
发表于 2018-3-9 12:58:20 | 显示全部楼层
mysql我发现错误日志,不知道是否跟卡死有关??

The InnoDB memory heap is disabled
使用道具 举报 回复 支持 反对
发表于 2018-3-9 13:01:49 | 显示全部楼层
180308 14:42:47 [Note] Plugin 'FEDERATED' is disabled.
180308 14:42:47 InnoDB: The InnoDB memory heap is disabled
180308 14:42:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180308 14:42:47 InnoDB: Compressed tables use zlib 1.2.7
180308 14:42:47 InnoDB: Using Linux native AIO
180308 14:42:47 InnoDB: Initializing buffer pool, size = 16.0M
180308 14:42:47 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /www/server/data/ibdata1 did not exist:
InnoDB: a new database to be created!
180308 14:42:47  InnoDB: Setting file /www/server/data/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
180308 14:42:47  InnoDB: Log file /www/server/data/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
180308 14:42:47  InnoDB: Log file /www/server/data/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
180308 14:42:47  InnoDB: Waiting for the background threads to start
180308 14:42:48 InnoDB: 5.5.59 started; log sequence number 0
180308 14:42:48 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180308 14:42:48 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180308 14:42:48 [Note] Server socket created on IP: '0.0.0.0'.
180308 14:42:49 [Note] Event Scheduler: Loaded 0 events
180308 14:42:49 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.59-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
180308 14:42:51 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

180308 14:42:51 [Note] Event Scheduler: Purging the queue. 0 events
180308 14:42:51  InnoDB: Starting shutdown...
180308 14:42:52  InnoDB: Shutdown completed; log sequence number 1595675
180308 14:42:52 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

180308 14:42:53 [Note] Plugin 'FEDERATED' is disabled.
180308 14:42:53 InnoDB: The InnoDB memory heap is disabled
180308 14:42:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180308 14:42:53 InnoDB: Compressed tables use zlib 1.2.7
180308 14:42:53 InnoDB: Using Linux native AIO
180308 14:42:53 InnoDB: Initializing buffer pool, size = 16.0M
180308 14:42:53 InnoDB: Completed initialization of buffer pool
180308 14:42:53 InnoDB: highest supported file format is Barracuda.
180308 14:42:53  InnoDB: Waiting for the background threads to start
180308 14:42:54 InnoDB: 5.5.59 started; log sequence number 1595675
180308 14:42:54 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180308 14:42:54 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180308 14:42:54 [Note] Server socket created on IP: '0.0.0.0'.
180308 14:42:54 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.59-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
180308 14:43:01 [Note] Plugin 'FEDERATED' is disabled.
180308 14:43:01 InnoDB: The InnoDB memory heap is disabled
180308 14:43:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180308 14:43:01 InnoDB: Compressed tables use zlib 1.2.7
180308 14:43:01 InnoDB: Using Linux native AIO
180308 14:43:01 InnoDB: Initializing buffer pool, size = 16.0M
180308 14:43:01 InnoDB: Completed initialization of buffer pool
180308 14:43:01 InnoDB: highest supported file format is Barracuda.
180308 14:43:02  InnoDB: Waiting for the background threads to start
180308 14:43:03 InnoDB: 5.5.59 started; log sequence number 1595675
180308 14:43:03 [Note] Recovering after a crash using mysql-bin
180308 14:43:03 [Note] Starting crash recovery...
180308 14:43:03 [Note] Crash recovery finished.
180308 14:43:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180308 14:43:03 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180308 14:43:03 [Note] Server socket created on IP: '0.0.0.0'.
180308 14:43:03 [Note] Event Scheduler: Loaded 0 events
180308 14:43:03 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.59-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
180309 11:52:50 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

180309 11:52:50 [Note] Event Scheduler: Purging the queue. 0 events
180309 11:52:50  InnoDB: Starting shutdown...
180309 11:52:52  InnoDB: Shutdown completed; log sequence number 3919289
180309 11:52:52 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

180309 11:52:52 [Note] Plugin 'FEDERATED' is disabled.
180309 11:52:52 InnoDB: The InnoDB memory heap is disabled
180309 11:52:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180309 11:52:52 InnoDB: Compressed tables use zlib 1.2.7
180309 11:52:52 InnoDB: Using Linux native AIO
180309 11:52:52 InnoDB: Initializing buffer pool, size = 256.0M
180309 11:52:53 InnoDB: Completed initialization of buffer pool
180309 11:52:53 InnoDB: highest supported file format is Barracuda.
180309 11:52:53  InnoDB: Waiting for the background threads to start
180309 11:52:54 InnoDB: 5.5.59 started; log sequence number 3919289
180309 11:52:57 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180309 11:52:57 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180309 11:52:57 [Note] Server socket created on IP: '0.0.0.0'.
180309 11:53:27 [Note] Event Scheduler: Loaded 0 events
180309 11:53:27 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.59-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

Status information:

Current dir: /www/server/data/
Running threads: 2  Stack size: 262144
Current locks:
lock: 0x2b340400a8d0:

lock: 0x39c8620:

lock: 0x3990d90:

lock: 0x3986180:

lock: 0x39797f0:

lock: 0x3977070:

lock: 0x3962760:

lock: 0x395d4a0:

lock: 0x3956f70:

lock: 0x394eae0:

lock: 0xfba420:

lock: 0xfba960:

lock: 0xfbaa20:

lock: 0xfbaae0:

lock: 0xfba4e0:

lock: 0xfba5a0:

lock: 0xfba360:

lock: 0xfba1e0:

lock: 0xfba2a0:

lock: 0xfbaba0:

lock: 0xfba660:

lock: 0xfba8a0:

lock: 0xfba7e0:

lock: 0xfba720:

lock: 0xfb9fa0:

lock: 0xfba060:

lock: 0xfba120:


Key caches:
default
Buffer_size:     134217728
Block_size:           1024
Division_limit:        100
Age_limit:             300
blocks used:             0
not flushed:             0
w_requests:              0
writes:                  0
r_requests:              0
reads:                   0


handler status:
read_key:            2
read_next:           0
read_rnd             0
read_first:          5
write:            1248
delete               0
update:              0

Table status:
Opened tables:         35
Open tables:           28
Open files:            21
Open streams:           0

Alarm status:
Active alarms:   0
Max used alarms: 0
Next alarm time: 0

Memory status:
Non-mmapped space allocated from system: 20951040
Number of free chunks:                         47
Number of fastbin blocks:                 0
Number of mmapped regions:                 16
Space in mmapped regions:                 221495296
Maximum total allocated space:                 0
Space available in freed fastbin blocks: 0
Total allocated space:                         11877616
Total free space:                         9073424
Top-most, releasable space:                 3920112
Estimated memory (with thread stack):    242970624



Events status:
LLA = Last Locked At  LUA = Last Unlocked At
WOC = Waiting On Condition  DL = Data Locked

Event scheduler status:
State      : INITIALIZED
Thread id  : 0
LLA        : n/a:0
LUA        : n/a:0
WOC        : NO
Workers    : 0
Executed   : 0
Data locked: NO

Event queue status:
Element count   : 0
Data locked     : NO
Attempting lock : NO
LLA             : init_queue:139
LUA             : init_queue:149
WOC             : NO
Next activation : never
180309 11:57:14 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

180309 11:57:14 [Note] Event Scheduler: Purging the queue. 0 events
180309 11:57:14  InnoDB: Starting shutdown...
180309 11:57:15  InnoDB: Waiting for 1 pages to be flushed
180309 11:57:15  InnoDB: Shutdown completed; log sequence number 3919299
180309 11:57:15 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

使用道具 举报 回复 支持 反对
发表于 2018-3-9 15:04:57 | 显示全部楼层
JackYeow 发表于 2018-3-9 12:24
这个tmp_table_size原来是8,现在我调到128,内存占用还是没下来,78%,郁闷,老大还有哪里可以优化的? ...

没用,我都调到4096了,wordpress软件的问题,无解!
使用道具 举报 回复 支持 反对
发表于 2018-3-9 15:22:29 | 显示全部楼层
penn 发表于 2018-3-9 15:04
没用,我都调到4096了,wordpress软件的问题,无解!

但是我用lnmp没有问题啊~~
使用道具 举报 回复 支持 反对
发表于 2018-3-9 15:49:53 | 显示全部楼层
1H1G   跑Wordpress  怎么优化都是坑的。换程序或者升级配置吧。
使用道具 举报 回复 支持 反对
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

普通问题处理

论坛响应时间:72小时

问题处理方式:排队(仅解答)

工作时间:白班:9:00 - 18:00

紧急运维服务

响应时间:3分钟

问题处理方式:宝塔专家1对1服务

工作时间:工作日:9:00 - 18:30

宝塔专业团队为您解决服务器疑难问题

点击联系技术分析

工作时间:09:00至18:30

快速回复 返回顶部 返回列表