source/adminguide/locale/zh_CN/LC_MESSAGES/tuning.mo (17 lines of code) (raw):
�� � | | B } � � � " j # � P � y � | � $ � ) � \ � ` ) � � � ( � 0 K 4
B �
�
� �
7 � � = � 0 K F g � � � 6 � � a � $ < : V w � � � ,
� : $ 8 - ] � Change the command-line parameter -XmxNNNm to a higher value of N. Configure XenServer dom0 Memory Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `Citrix Knowledgebase Article <http://support.citrix.com/article/CTX126531>`_.The article refers to XenServer 5.6, but the same information applies to XenServer 6 Edit the MySQL configuration file: Edit the Tomcat configuration file: For example, if the current value is -Xmx128m, change it to -Xmx1024m or higher. For more information about memory issues, see "FAQ: Memory" at `Tomcat Wiki. <http://wiki.apache.org/tomcat/FAQ/Memory>`_ For more information about the buffer pool, see "The InnoDB Buffer Pool" at `MySQL Reference Manual <http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pool.html>`_. Host and guest performance monitoring is available to end users and administrators. This allows the user to monitor their utilization of resources and determine when it is appropriate to choose a more powerful service offering or larger disk. If the Management Server is subject to high demand, the default maximum JVM memory allocation can be insufficient. To increase the memory: Increase Management Server Maximum Memory Insert the following line in the [mysqld] section, below the datadir line. Use a value that is appropriate for your situation. We recommend setting the buffer pool at 40% of RAM if MySQL is on the same server as the management server or 70% of RAM if MySQL has a dedicated server. The following example assumes a dedicated server with 1024M of RAM. It is important to provide enough memory space for the MySQL database to cache data and indexes: Performance Monitoring Restart the MySQL service. Set Database Buffer Pool Size Set and Monitor Total VM Limits per Host The CloudStack administrator should monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are automatically redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster at all times. Keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) \* (per-host-limit). Once a cluster reaches this number of VMs, use the CloudStack UI to disable allocation of more VMs to the cluster. This section provides tips on how to improve the performance of your cloud. To put the new setting into effect, restart the Management Server. Tuning Project-Id-Version: Apache CloudStack Administration RTD
Report-Msgid-Bugs-To:
POT-Creation-Date: 2014-06-30 12:52+0200
PO-Revision-Date: 2014-06-30 12:04+0000
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Language: zh_CN
Plural-Forms: nplurals=1; plural=0;
改变命令行参数 -XmxNNNm中的N为更高的值。 配置XenServer dom0内存 配置XenServer为dom0分配更多的内存，可使XenServer处理更多的虚拟机。我们推荐为dom0设置的内存数值为2940 MB。至于如何操作，可以参阅如下URL： `Citrix 知识库文章 <http://support.citrix.com/article/CTX126531>`_.。这篇文章同时适用于XenServer 5.6和6.0版本。 编辑MySQL配置文件： 编辑Tomcat配置文件： 例如，如果当前值为 -Xmx128m，则改为 -Xmx1024m或更高。 欲了解更多管理内存问题的详细信息，请参阅"FAQ:内存" 在 `Tomcat Wiki. <http://wiki.apache.org/tomcat/FAQ/Memory>`_ 欲了解更多关于缓冲池的信息，请参阅"InnoDB缓冲池" `MySQL参考手册<http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pool.html>`_. 终端用户和管理员都能使用宿主机和虚拟机的性能监控。性能监控将允许用户监控他们的资源利用并且帮助用户决定何时将需要选择一个更高性能的服务或者更大的硬盘。 如果管理服务器用于高需求，默认JVM的最大内存分配可能不足。增加内存: 增加管理服务器到最大内存 在 [mysqld]部分的datadir下面插入如下行。使用适合您情况的值。如果MySQL和管理服务器在同一台服务器上面我们建议设置缓冲池为内存的40%，如果MySQL为专用的服务器我们建议设置为内存的70%。下面的示例假设一台专用的服务器的内存为1024M。 为MySQL数据库提供足够的内存空间来缓存数据和索引是很重要的： 性能监控 重启MySQL服务. 设置数据库缓冲池大小 设置和监控每个主机的总VM数限制 管理员应该监视每个集群中的虚拟机实例的总数，如果总量快达到hypervisor允许的最大虚拟机数量时，不再向此群集分配虚拟机。并且，要注意为主机预留一定的计算能力，以防止群集中有主机发生故障,因为发生故障的主机上的虚拟机需要重新部署在这些预留主机上。请咨询您所选择hypervisor的文档，了解此hypervisor能支持的最大虚拟机数量，并将此数值设置在CloudStack的全局设置里。监控每个群集里虚拟机的活跃程序，并将活跃虚拟机保持在一个安全线内。这样，CloudStack就能允许偶尔的主机故障。举个示例：如果集群里有N个主机，而你只能让其中任一主机的停机时间不超过特定时间。那么，你能在此集群部署的最多虚拟主机数量值为：(N-1) \* (每主机最大虚拟量数量限值)。一旦群集中的虚拟机达到此数量，必须在CloudStack的用户界面中禁止向此群集分配新的虚拟机。 本节提示如何提高云性能。 将新的设置生效，重启管理服务。 调优