Operating System - OpenVMS
1824936
Members
3967
Online
109678
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2007 08:34 AM
тАО10-17-2007 08:34 AM
TDC
I was wondering if anyone had information about how the tdc collects disk I/O. After extracting the data collection file there are three fields for total bytes read. DSK.TDC_DSK_RD_IOCNT
DSK.TDC_DSK_RD_LOGIOCNT
DSK.TDC_DSK_RD_PHYIOCNT
Does anyone what the difference between these three are. I cant seem to be able to generate any realistic data for disk reads and writes i have generated reads and writes and not seen any data that will recognize this.
thanks
thanks
DSK.TDC_DSK_RD_LOGIOCNT
DSK.TDC_DSK_RD_PHYIOCNT
Does anyone what the difference between these three are. I cant seem to be able to generate any realistic data for disk reads and writes i have generated reads and writes and not seen any data that will recognize this.
thanks
thanks
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2007 10:15 AM
тАО10-17-2007 10:15 AM
Re: TDC
justin,
Logical I/O is an I/O sent to the file system. It's specified in terms of file system structures. Physical I/O is directed at the physical disk. It's specified in terms of disk structure (obviously, a LOGIO is at some stage converted into a PHYIO, but I'd guess that PHYIOs generated as a result of a LOGIO are not counted in your statistics)
IOCNT count be the sum of LOGIO and PHYIO, or it could count all I/Os that are directed to the device, even if they're serviced by a cache somewhere along the way. (sorry, I don't know how TDC defines the fields, have you looked in the documentation?).
What do you mean by "I cant seem to be able to generate any realistic data for disk reads and writes". What does your data look like, and why do you think it's unrealistic?
Make sure you remember that there are numerous layers of software between your programs and the disk surface. Thus, if you have a program that reads the same record in a file numerous times, there are potentially several places where that data might be cached, so even if you generate 100 reads, you may only see a single read I/O (indeed, you should hope that is the case!). Similarly, if you write the same record, or several nearby records, even numerous times, the updates may coalesce into a single write I/O.
Disk I/O is comparatively VERY expensive, so software does it's best to only go out to disk when absolutely necessary (pop quiz... if we scale up the time it takes for a CPU to add 2 integers, calling it 1 second. On that time scale, how long does a disk read from a locally attached drive take?)
You can trust that the data collected is accurate. What's the real problem you're trying to solve?
Logical I/O is an I/O sent to the file system. It's specified in terms of file system structures. Physical I/O is directed at the physical disk. It's specified in terms of disk structure (obviously, a LOGIO is at some stage converted into a PHYIO, but I'd guess that PHYIOs generated as a result of a LOGIO are not counted in your statistics)
IOCNT count be the sum of LOGIO and PHYIO, or it could count all I/Os that are directed to the device, even if they're serviced by a cache somewhere along the way. (sorry, I don't know how TDC defines the fields, have you looked in the documentation?).
What do you mean by "I cant seem to be able to generate any realistic data for disk reads and writes". What does your data look like, and why do you think it's unrealistic?
Make sure you remember that there are numerous layers of software between your programs and the disk surface. Thus, if you have a program that reads the same record in a file numerous times, there are potentially several places where that data might be cached, so even if you generate 100 reads, you may only see a single read I/O (indeed, you should hope that is the case!). Similarly, if you write the same record, or several nearby records, even numerous times, the updates may coalesce into a single write I/O.
Disk I/O is comparatively VERY expensive, so software does it's best to only go out to disk when absolutely necessary (pop quiz... if we scale up the time it takes for a CPU to add 2 integers, calling it 1 second. On that time scale, how long does a disk read from a locally attached drive take?)
You can trust that the data collected is accurate. What's the real problem you're trying to solve?
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2007 10:50 AM
тАО10-17-2007 10:50 AM
Re: TDC
Thanks for your response
What Im trying to do is to use the information from TDC to graph disk I/O. This will be very usefull to see what disks are used most and when.
What ive been doing is running the data collector on a node and generating disk reads and writes in ten minute intervals(its a test node all its running is the data collector). I cant see any increase in reads or writes in the data. Also when I generate the graphs there is an average of about 20MB being written when nothing is running on the node except for the data collector.
What Im trying to do is to use the information from TDC to graph disk I/O. This will be very usefull to see what disks are used most and when.
What ive been doing is running the data collector on a node and generating disk reads and writes in ten minute intervals(its a test node all its running is the data collector). I cant see any increase in reads or writes in the data. Also when I generate the graphs there is an average of about 20MB being written when nothing is running on the node except for the data collector.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2007 11:06 AM
тАО10-17-2007 11:06 AM
Re: TDC
justin,
>Also when I generate the graphs there is
>an average of about 20MB being written
>when nothing is running on the node except
>for the data collector.
What do you suppose the data collector does with the data it collects? Ask Mr Heinsenberg ;-)
>generating disk reads and writes in ten
>minute intervals(its a test node all its
>running is the data collector). I cant see
>any increase in reads or writes in the data
Try:
$ SHOW MEM/CACHE/FULL
XFC is a wonderous thing. If there's nothing else running, there's LOTS of available memory to cache stuff. I know of a system that ran for an entire week with the system disk popped out of the storage shelf. Everything was handled out of cache.
It's VERY difficult to design a realistic benchmark program for disk I/O.
>Also when I generate the graphs there is
>an average of about 20MB being written
>when nothing is running on the node except
>for the data collector.
What do you suppose the data collector does with the data it collects? Ask Mr Heinsenberg ;-)
>generating disk reads and writes in ten
>minute intervals(its a test node all its
>running is the data collector). I cant see
>any increase in reads or writes in the data
Try:
$ SHOW MEM/CACHE/FULL
XFC is a wonderous thing. If there's nothing else running, there's LOTS of available memory to cache stuff. I know of a system that ran for an entire week with the system disk popped out of the storage shelf. Everything was handled out of cache.
It's VERY difficult to design a realistic benchmark program for disk I/O.
A crucible of informative mistakes
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP