| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Philippe Poelvoorde | Date: | April 7 2006 8:35am |
| Subject: | Re: MySQL 4.1.11 innodb cache can't be flushed after restart ? | ||
| View as plain text | |||
2006/4/7, Charles Q. Shen <qs2005@stripped>: > The OS used are Mandriva and Fedora. > > Can you explain more? > I'll make it quick, there is plenty of doc on a web that will explain this better than I can. Once you read few things from your hard drive (let's say the index file for your table), it's kept in memory. Next time you access it it's directly retrived from memory, not the hard drive, thus low response time. shutting down MySQL won't clear that cache. If you want to circumvent that, you need to umount the partition where data and index are stored. HIMH http://www.tldp.org/LDP/tlk/fs/filesystem.html
| Thread | ||
|---|---|---|
| • MySQL 4.1.11 innodb cache can't be flushed after restart ? | Charles Q. Shen | 7 Apr |
| • Re: MySQL 4.1.11 innodb cache can't be flushed after restart ? | Philippe Poelvoorde | 7 Apr |
| • RE: MySQL 4.1.11 innodb cache can't be flushed after restart ? | Charles Q. Shen | 7 Apr |
| • Re: MySQL 4.1.11 innodb cache can't be flushed after restart ? | Philippe Poelvoorde | 7 Apr |
| • RE: MySQL cache problem - innodb_buffer_pool_size and FS cache | Charles Q. Shen | 15 Apr |
| • Re: MySQL cache problem - innodb_buffer_pool_size and FS cache | Dan Nelson | 15 Apr |
| • RE: MySQL cache problem - innodb_buffer_pool_size and FS cache | Charles Q. Shen | 15 Apr |
| • Re: MySQL cache problem - innodb_buffer_pool_size and FS cache | Dan Nelson | 16 Apr |
| • Should we petition GoDaddy? | Nicolas Verhaeghe | 16 Apr |
| • RE: Should we petition GoDaddy? | David T. Ashley | 16 Apr |
| • Re: Should we petition GoDaddy? | James Eaton | 17 Apr |
| • Re: Should we petition GoDaddy? | David Logan | 17 Apr |
| • Re: Should we petition GoDaddy? | Dotan Cohen | 17 Apr |
