Difference: SystemAdministratorGuideForEMI1 (26 vs. 27)

Revision 272011-09-06 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="SystemAdministratorDocumentation"

System Administrator Guide for CREAM for EMI-1 release

Line: 653 to 638
 
JAVA_OPTS setting -Xms128m -Xmx512m -Xms512m -Xmx1024m -Xms512m -Xmx2048m

After having done the changes, it is necessary to restart tomcat

Added:
>
>

0.1 MySQL database configuration guidelines

Default values of some MySQL settings are likely to be suboptimal especially for large machines. In particular some parameters could improve the overall performance if carefully tuned.
In this context one relevant parameter to be set is the innodb_buffer_poll_size which specifies the size of the buffer pool (the default value is 8MB).

The benefits obtained by using a proper value for this parameter are principally: an appreciable performance improving and the reduced amount of disk I/O needed for accessing the data in the tables. The optimal value depends on the amount of physical memory and the CPU architecture available in the host machine.

The maximum value depends on the CPU architecture, 32-bit or 64-bit. For 32-bit systems, the CPU architecture and operating system sometimes impose a lower practical maximum size.
Larger this value is set, less disk I/O is needed to access data in tables. On a dedicated database server, it is possible to set this to up to 80% of the machine physical memory size.
Scale back this value whether one of the following issues occur:

  • competition for physical memory might cause paging in the operating system;
  • innoDB reserves additional memory for buffers and control structures, so that the total allocated space is approximately 10% greater than the specified size.

In /etc/my.cnf, in particular within the [mysqld] section, it is suggested to customize the innodb_buffer_pool_size parameter taking into account how much physical memory is available.

Example:

[mysqld]
innodb_buffer_pool_size=512MB

After that, it's necessary to restart the mysql service for applying the change:

/etc/init.d/mysqld restart

Finally, the following sql command (root rights are needed) could be used for checking if the new value was applied successfully:

SHOW VARIABLES like 'innodb_buffer_pool_size';
 

0.1 How to start the CREAM service

Line: 726 to 739
 }
Deleted:
<
<
 

0.0.1 Security recommendations

Security recommendations relevant for the CREAM CE is available in http://wiki.italiangrid.org/twiki/bin/view/CREAM/ServiceReferenceCard#Security_recommendations

Line: 900 to 911
 

0.1 How to check if you are using the old or the new blparser

Changed:
<
<
If you want to quickly check if you are using the old or the new BLAH Blparser, do a grep registry blah.config. If you see something like:
>
>
If you want to quickly check if you are using the old or the new BLAH Blparser, do a grep registry blah.config. If you see something like:
 
# grep registry blah.config
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback