SpirirHost Support Centre: MySQL Reference Manual p.363

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Chapter 5: MySQL Optimisation 363 table cache is full, because for every table that has to be opened, another must be closed. You can reduce this overhead by making the table cache larger. 5.5 Optimising the MySQL Server 5.5.1 System/Compile Time and Startup Parameter Tuning We start with the system level things since some of these decisions have to be made very early. In other cases a fast look at this part may suce because it not that important for the big gains. However, it is always nice to have a feeling about how much one could gain by changing things at this level. The default OS to use is really important! To get the most use of multiple-CPU machines one should use Solaris (because the threads works really nice) or Linux (because the 2.2 kernel has really good SMP support). Also on 32-bit machines Linux has a 2G le-size limit by default. Hopefully this will be xed soon when new lesystems are released (XFS/Reiserfs). If you have a desperate need for les bigger than 2G on Linux-intel 32 bit, you should get the LFS patch for the ext2 lesystem. Because we have not run MySQL in production on that many platforms, we advice you to test your intended platform before choosing it, if possible. Other tips: If you have enough RAM, you could remove all swap devices. Some operating systems will use a swap device in some contexts even if you have free memory. Use the --skip-external-locking MySQL option to avoid external locking. Note that this will not impact MySQL's functionality as long as you only run one server. Just remember to take down the server (or lock relevant parts) before you run myisamchk. On some system this switch is mandatory because the external locking does not work in any case. The --skip-external-locking option is on by default when compiling with MIT- pthreads, because flock() isn't fully supported by MIT-pthreads on all platforms. It's also on default for Linux as Linux le locking are not yet safe. The only case when you can't use --skip-external-locking is if you run multiple MySQL servers (not clients) on the same data, or run myisamchk on the table without rst ushing and locking the mysqld server tables rst. You can still use LOCK TABLES/UNLOCK TABLES even if you are using --skip-external- locking 5.5.2 Tuning Server Parameters You can get the default buer sizes used by the mysqld server with this command: shell> mysqld --help

MySQL Reference Manual

Home
Hosting Plans \| Domain Registration \| About Us \| Contact Us \| Site Map Terms of Use \| Privacy Policy \| Guarantees Merchant Accounts

SpiritHost - web hosting for spiritual and education sites SpiritHit.com - Religious and Spiritual Portal Copyright © 2002 Dyntex Group, Inc. All Rights Reserved

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide