全球主机交流论坛

 找回密码
 注册

QQ登录

只需一步,快速开始

CeraNetworks网络延迟测速工具IP归属甄别会员请立即修改密码
楼主: leozhang

[Windows VPS] nginx高手进来看看这个神马情况? linode768内存,

[复制链接]
发表于 2012-1-25 09:59:10 | 显示全部楼层
阿帕奇处理动态 ngx处理静态
 楼主| 发表于 2012-1-25 10:13:54 | 显示全部楼层
wdlth 发表于 2012-1-20 21:47
搜 tuning-primer.sh ,就有很多资料。
不过还是看官方文档认清参数比较好。

   -- MYSQL PERFORMANCE TUNING PRIMER --
             - By: Matthew Montgomery -

MySQL Version 5.0.84 i686

Uptime = 0 days 0 hrs 5 min 28 sec
Avg. qps = 77
Total Questions = 25387
Threads Connected = 1

Warning: Server has not been running for at least 48hrs.
It may not be safe to use these recommendations

To find out more information on how each of these
runtime variables effects performance visit:
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html
Visit http://www.mysql.com/products/enterprise/advisors.html
for info about MySQL's Enterprise Monitoring and Advisory Service

SLOW QUERIES
The slow query log is NOT enabled.
Current long_query_time = 10 sec.
You have 0 out of 25408 that take longer than 10 sec. to complete
Your long_query_time seems to be fine

BINARY UPDATE LOG
The binary update log is NOT enabled.
You will not be able to do point in time recovery
See http://dev.mysql.com/doc/refman/5.0/en/point-in-time-recovery.html

WORKER THREADS
Current thread_cache_size = 8
Current threads_cached = 4
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 400
Current threads_connected = 2
Historic max_used_connections = 6
The number of used connections is 1% of the configured maximum.
You are using less than 10% of your configured max_connections.
Lowering max_connections could help to avoid an over-allocation of memory
See "MEMORY USAGE" section to make sure you are not over-allocating

INNODB STATUS
Current InnoDB index space = 132 M
Current InnoDB data space = 232 M
Current InnoDB buffer pool free = 91 %
Current innodb_buffer_pool_size = 640 M
Depending on how much space your innodb indexes take up it may be safe
to increase this value to up to 2 / 3 of total system memory

MEMORY USAGE
Max Memory Ever Allocated : 854 M
Configured Max Per-thread Buffers : 4.02 G
Configured Max Global Buffers : 792 M
Configured Max Memory Limit : 4.80 G
Physical Memory : 750 M

Max memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 2 M
Current key_buffer_size = 7 M
Key cache miss rate is 1 : 134
Key buffer free ratio = 88 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 128 M
Current query_cache_used = 9 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 7.38 %
Current query_cache_min_res_unit = 4 K
Your query_cache_size seems to be too high.
Perhaps you can use these resources elsewhere
MySQL won't cache query results that are larger than query_cache_limit in size

SORT OPERATIONS
Current sort_buffer_size = 4 M
Current read_rnd_buffer_size = 2 M
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 0 queries where a join could not use an index properly
Your joins seem to be using indexes properly

OPEN FILES LIMIT
Current open_files_limit = 2000 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
Current table_cache value = 64 tables
You have a total of 447 tables
You have 64 open tables.
Current table_cache hit rate is 3%
, while 100% of your table cache is in use
You should probably increase your table_cache

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 128 M
Of 3036 temp tables, 6% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Created disk tmp tables ratio seems fine

TABLE SCANS
Current read_buffer_size = 4 M
Current table scan ratio = 6 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 0 : 26776
Your table locking seems to be fine
  tuning-primer的结果出来了,4核的XEN, 768内存.
发表于 2012-1-25 13:27:59 | 显示全部楼层
leozhang 发表于 2012-1-25 10:13
-- MYSQL PERFORMANCE TUNING PRIMER --
             - By: Matthew Montgomery -

把慢查询日志启用,把table_cache加大。
发表于 2012-1-25 13:39:06 | 显示全部楼层
360111697 发表于 2012-1-20 21:05
从不用nginx处理动态

nginx也从来不处理动态..........

评分

参与人数 1威望 +20 收起 理由
我是人 + 20 这句话,好像听圈圈说过。。。.

查看全部评分

 楼主| 发表于 2012-1-25 17:41:40 | 显示全部楼层
本帖最后由 leozhang 于 2012-1-25 17:42 编辑
4806569 发表于 2012-1-25 13:45
1G的linode,两个magento,IP每天5000多,暂时压力不大~嘿嘿


同道呀,用什么跑的? AP还是nginx load能稳在多少? 超过0.5不?
 楼主| 发表于 2012-1-25 17:48:49 | 显示全部楼层
4806569 发表于 2012-1-25 13:45
1G的linode,两个magento,IP每天5000多,暂时压力不大~嘿嘿

啥时候我才能五千多IP呀,,,晕...
发表于 2012-1-27 11:44:22 | 显示全部楼层
Kokgog 发表于 2012-1-25 13:39
nginx也从来不处理动态..........

nginx也从来不处理动态,确实如此,nginx本身并不能支持php,支持php的是php-fpm,以fastcgi形式运行
发表于 2012-1-27 11:39:28 | 显示全部楼层
你用的程序比较耗资源把。
发表于 2012-1-27 11:34:12 | 显示全部楼层
不会优化惹得祸
 楼主| 发表于 2012-1-27 10:49:04 | 显示全部楼层
4806569 发表于 2012-1-26 20:18
不到0.5
就LNMP得环境.
gap中国也是这环境,当然他们服务器多,促销时也挂过,呵呵.没啥问题的.apache老矣 ...

lnmp的安装包,我一直装不上magento
不知道怎么回事,能把你的MYSQL的配置发来参考下不,我觉得我的MYSQL配置 肯定有问题,
您需要登录后才可以回帖 登录 | 注册

本版积分规则

Archiver|手机版|小黑屋|全球主机交流论坛

GMT+8, 2025-9-12 17:33 , Processed in 0.076653 second(s), 12 queries , Gzip On, MemCache On.

Powered by Discuz! X3.4

© 2001-2023 Discuz! Team.

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