- 3 Using Falcon
- 3.1 Configuration Parameters
- 3.2 Creating the Falcon Tablespace
- 3.3 Creating Tables and Indexes within Falcon
- 3.4 Principles and Terminology
- 3.5 Limits
To get the best out of the Falcon engine you should understand the following basic principles and terminology.
The MySQL Falcon architecture combines advanced techniques with a simplified structure that results in a high-performance transactional database that requires little maintenance or troubleshooting by the database administrator.
User data file — stores the Falcon data.
Falcon serial log — contains recently committed data changes, index changes and transactional information. Also provides data recovery facilities.
Page cache — holds database pages being read or written.
Record cache — holds copies of active and uncommitted records.
System memory — contains transaction context information, index accelerators and system metadata.
Work Threads — are background threads. There are two threads, the "gopher" thread moves data from the Falcon Serial Log into the database page cache and from the page cache to disk. The second is the page writer thread which writes blob pages.
