Timeline for answer to dd's relation with page cache by John Mahowald
Current License: CC BY-SA 3.0
Post Revisions
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 10:02 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jul 13, 2017 at 13:35 | comment | added | Jepsenwan | Thanks John. I just realized that the hugepage is much bigger than page in disk. Besides. Hugepage is pined in main memory. So it wont have anything to do with page cache. | |
| Jul 13, 2017 at 13:15 | comment | added | John Mahowald | Huge pages cannot be used as as page cache or a few other uses, no. Which means tuning for databases involves sizing pages correctly. This is a broad topic and really a different question, I recommend reading a tuning guide for that database. | |
| Jul 13, 2017 at 10:13 | comment | added | Jepsenwan | Thanks John. An extra question.Under any circumstance the hugepage will be employed as page cache? For instance, in system running a Oracle database. | |
| Jul 12, 2017 at 10:47 | comment | added | John Mahowald | Yes. Caches are not dropped until there is not enough free memory for other demands. | |
| Jul 12, 2017 at 3:55 | comment | added | Jepsenwan | Thanks. I noticed if I issue the dd command again with the same arguments，it wont get the cached number that's returned by free command increased despite the execution of sync command. Is this because the page cache hit？ | |
| Jul 12, 2017 at 3:47 | vote | accept | Jepsenwan | ||
| Jul 10, 2017 at 1:39 | history | answered | John Mahowald | CC BY-SA 3.0 |