Monitor disk io on linux server with iotop and cron. Iotop Disk Input Output usage. Recently my server was giving notifications of disk io activity rising above a certain threshold at regular intervals. My first guess was that some cronjob task was causing that. So I tried to check various cron tasks to find out which task or process was causing the io burst. On servers specially its always a good practice to monitor resource usage to make sure that websites work fast and well. However searching manually is not quite easy and this is where utilities like iotop come in. Its quite easy to use. Just run it from a terminal and you should see some output like this. Total DISK READ 0. Bs Total DISK WRITE 1. Download Adobe Pagemaker 7 Manual Pdf'>Download Adobe Pagemaker 7 Manual Pdf. Ks. TID PRIO USER DISK READ DISK WRITE SWAPIN IO COMMAND. Bs 9. 8. 5. 6 Ks 0. Bs 0. 0. 0 Bs 0. Bs 0. Bs 0. Bs 0. Bs 0. Bs 0. 0. 0 Bs 0. Bs 0. 0. 0 Bs 0. Bs 0. Bs 0. H. 4. 10. 2 be4 www data 0. Bs 0. 0. 0 Bs 0. Bs 0. Bs 0. H. 8 rt4 root 0. This tutorial shows how to monitor disk io on a linux server automatically with iotop and cron. As we can see, each row shows a certain process and the amount of data it is reading or writing to. This information is actually instantaneous, so iotop keeps updating the values at certain interval like 1 second. Running iotop like this just tells the current io usage. What if we want to keep running iotop and record all io activity and analyse it later. This is where cron comes in. Automatic logging via cron. Cron will run iotop in the background and record io usage details to a file that can be analysed later. Here is the basic iotop command that we want to run in the background via cron. Ks 7. 6. 4 Ks 0. Ks 1. Ks 0. Ks 7. 6. 2 Ks 0. Ks 7. 6. 2 Ks 0. Ks 1. Ks 0. Note that iotop must be run with root privileges. So use sudo on ubuntu for example. Now the most important option used in the above command is the b option which is for batchnon interactive mode. Whm Complete Solution' title='Whm Complete Solution' />In batch mode iotop will keep outputting line after line instead of showing a long list that updates automatically. This is necessary when we want to log io activity over a certain period of time. The other option called o will show only those processes which actually did some io activity. Otherwise iotop would show all processes. The t option adds a timestamp which adds further information if you want to track a specific high io process. The k option shows all figures in kilobytes. To help you build better and more successful websites and to manage your web hosting account easier, weve created a set of stepbystep tutorials. On this. India. to web hosting are a professional web solution company, which provide excellent support services. Parasite City Full Game. Support tickets are quickly answered, your always updated. Hi Abap OO Pros, I have been trying to create a OO Class for usage in an endroutine of a BI transformation. There are some papers and discussions on it I have been. JaguarPC provide professional web hosting services since 1988. Exceptional service, affordable web hosting plans, daily backups, free domain transfer and more. Whm Complete Solution' title='Whm Complete Solution' />To log the output we simply need to redirect it to a file. The best place is varlog and the file could be named iotop. So here is the next command iotop botqqqk iter6. This will run iotop for 6. Now the command has to be run every minute which cron would do easily. Setup cron as root. Get into your linux server as root and create a file etccron. Add to this file our earlier iotop command that would log the iotop output. Simple Now cron would run the command every minute and every time the command would run for a minute taking samples as 1 second interval and all activity gets logged to varlogiotop. Make sure to mention the full path to iotop otherwise cron might not be able to run it at all. To find the location of iotop on your linux server, use the which command which iotop. Monitor only high io processes. I had to setup this io monitoring because my linux server was giving high io alerts at around 3 AM in the morning when I could not get up to check manually. And since the server alert was showing high disk io activity I decided to monitor only those processes that did high disk io. Here is a simple command that greps the iotop output to grab process that have over 1. P dd. dd Ks. Ks 4. Ks 0. Ks 1. 52. 3. Ks 0. Ks 2. 2. 8. Ks 0. Ks 2. 6. 5. Ks 0. Ks 1. 9. 0. Ks 0. So it would not show those process that had less than 1. Ks of disk io. It does so by filtering the output using grep and regular expressions. This is very useful when we want to find any process that is causing very high io activity. High activity would mean around 1 Ms of disk activity for some time. So grepping for values with 4 digits will find those processes right away. To add the same command to cron replace the earlier command like this root usrsbiniotop botqqqk iter6. P dd. dd Ks varlogiotop. I used it, and it works quite well. Here is how the output looks when filtered using grep to show only high io process entries. Ks 1. 89. 7. 7. 4 Ks 0. Ks 1. 07. 1. 0. 7 Ks 0. Ks 1. 46. 9. 1. 7 Ks 0. Ks 0. 0. 0 Ks 0. Ks 8. Ks 0. Ks 1. 35. 4. Ks 0. Ks 1. 14. 6. Ks 0. Ks 1. 49. 4. Ks 0. Ks 2. 87. 8. Ks 0. Ks 2. 69. 4. Ks 0. So try it out on your server. Last Updated On 2. October 2. 01. 3. Searching for generic approach using classes in Bi Transformation Routines. I think moving the working code of routines right out of the transformation is a good idea not only does it mean you can change the code without having to reactivate the transformation, but it also gives you full version management. Its the approach Ive followed for the past ten years or so of developing in BW. For your example, there are three fields that need to be accessed, FISCPER, FISCPER3 and FISCYEAR. This is how I would write it. DATA begin of fieldsofinterest. TYPE bicoic. 0finprio. FIELD SYMBOLS lt record TYPE ANY. LOOP AT resultpack ASSIGNING lt record. MOVE CORRESPONDING lt record TO fieldsofinterest. READ TABLE gtmdcofpr ASSIGNING lt mdocfpr WITH TABLE KEY bicc. CHECK sy subrc IS INITIAL. MOVE CORRESPONDING lt mdocfpr TO lt record. Table gtmdcofpr should be defined something like HASHED WITH UNIQUE KEY bicclfinprio. This assumes that table gtmdcofpr only has fields fiscper, fiscper. DATA begin of fieldsofinterest. TYPE bicoic. 0finprio. TYPE bi. 0fiscper. TYPE bi. 0fiscper. TYPE bi. 0fiscyear. FIELD SYMBOLS lt record TYPE ANY. LOOP AT resultpack ASSIGNING lt record. MOVE CORRESPONDING lt record TO fieldsofinterest. READ TABLE gtmdcofpr ASSIGNING lt mdocfpr WITH TABLE KEY bicc. CHECK sy subrc IS INITIAL. MOVE CORRESPONDING lt mdocfpr TO fieldsofinterest. MOVE CORRESPONDING fieldsofinterest TO lt record.