]]>
]]>

The patch is extracted from Google patches.

The patch adds information about where fsync call was initiated from. The information is available in SHOW INNODB STATUS output. There is BACKGROUND THREAD section (this is new section) with fsync callers

----------
BACKGROUND THREAD
----------
fsync callers: 609 buffer pool, 89 other, 86 checkpoint, 105 log aio, 126 log sync, 0 archive

And also patch extends LOG section

---
LOG
---

390 log i/o's done, 0.00 log i/o's/second, **126 syncs, 5384 checkpoints**
log sync callers: 29459 buffer pool, background 122 sync and 124 async, 110 internal, checkpoint 5384 sync and 0 async, 0 archive, commit 0 sync and 2 async
log sync syncers: 7 buffer pool, background 118 sync and 0 async, 0 internal, checkpoint 1 sync and 0 async, 0 archive, commit 0 sync and 0 async

It shows how many syncs and checkpoints for log were executed and sources of log sync callers. There difference between “caller” and “syncer” is that for “syncer” was used fsync call.

 
patches/innodb_fsync_source.txt · Last modified: 2011/07/17 21:05 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Contact Us 24 Hours A Day
SupportContact us 24×7
Emergency? Contact us for help now!
Sales North America(888) 316-9775 or
(208) 473-2904
Sales
Europe
+44-208-133-0309 (UK)
0-800-051-8984 (UK)
0-800-181-0665 (GER)
Training(855) 55TRAIN or
(925) 271-5054

 

Share This
]]> ]]>