| To: | Mark Seger <mjseger@xxxxxxxxx> |
|---|---|
| Subject: | Re: definitions for /proc/fs/xfs/stat |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Fri, 14 Jun 2013 20:17:30 -0400 (EDT) |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAC2B=ZHYV6d-1PO_=-jXsQidZnYPHVwcVAaQh2mxJt=5K03AEA@xxxxxxxxxxxxxx> |
| References: | <CAC2B=ZFP_Fg34aFpk857stgB7MGcrYs9tybRS-ttw1CXNeU41Q@xxxxxxxxxxxxxx> <91017249.1356192.1371248207334.JavaMail.root@xxxxxxxxxx> <CAC2B=ZHYV6d-1PO_=-jXsQidZnYPHVwcVAaQh2mxJt=5K03AEA@xxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | sfa8tEPoPyjq9/+Hn5TbIfiB6/RSEg== |
| Thread-topic: | definitions for /proc/fs/xfs/stat |
----- Original Message ----- > actually I have since found a decoder ring here - > http://xfs.org/index.php/Runtime_Stats and have been incorporating a lot of > the data so I can look at things in real time. I'd still love to know why Ah, good stuff. > writing 1000 1K files results in 200MB/sec of disk I/O though. clearly For how many seconds? (or fractions thereof?) You may need the level of detail that only tracing will provide to explore further, although off the top of my head I'm not sure exactly which events you should focus on (log, inode creation, or space allocation at a guess). cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: definitions for /proc/fs/xfs/stat, Mark Seger |
|---|---|
| Next by Date: | Re: [PATCH 1/3] xfs: don't shutdown log recovery on validation errors, Dave Chinner |
| Previous by Thread: | Re: definitions for /proc/fs/xfs/stat, Mark Seger |
| Next by Thread: | Re: definitions for /proc/fs/xfs/stat, Mark Seger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |