Monitoring Tools

 

Most or all tools mentioned from Google Automation: Trouble Shooting & Debugging Coursera course.

Resources include:
  • CPU 
    • top shows % cpu used;  system usage; Total should not be more than the # of cores
    • time <call to script or pgm>
  • the memory 
    • memcached
  • the disk IO
    • topio
  • the network connection
    • iftop - monitors bandwidth
  • the graphics card
  • multiple
    • ab -n <times> to get the average timing of <times> requests
  • code profilers
    • profilers are specific to each programming language. So we would use:
      • gprof to analyze a C program
      • c-Profile module to analyze a Python program.
      •  pprofile3 for example:
        • pprofile3 -f callgrind -o profile.out  <call to script or pgm>
        • kcachegrind  a graphical interface for looking into pprofile 3 output files
    • used to see 
      • which functions are called by our program, 
      • how many times each function was called and 
      • how much time are programs spent on each of them.
Where and what is the problem?
  • use the tools available in our operating system, 
  • monitor the usage of each resource, 
  • and then work out which one is blocking our programs for running faster.
Slowness caused some resource exhausted / overused
  • Mac - Activity Monitor
  • Windows - Resource Monitor and Performance Monitor 
  • Linux - top - which
Link List of Monitoring Tool information
Check out the following links for more information:

Comments

Post a Comment

Popular posts from this blog

Trouble Shooting & Debugging - Terms & Steps

Notes and basics from Google Automation: Trouble Shooting & Debugging Coursera course Trouble shooting - fixing system Debugging - fixing program code Cache stores data in a form that's faster to access than its original form.   M emory leak -  when memory which is no longer needed is not getting released.  WEEK 2 Videos - review for terms and steps! Debugging Process figuring out the problem and its solution require some creativity.  We need to come up with new ideas of what could be failing, and ways to check for that.  And once we know what's failing, we need to imagine how to solve it.  To take it a step further, once we've solved a problem, we can start thinking about how to prevent it from happening again Steps to solve a problem Gather information super important resource to solve a problem is the reproduction case , which is a clear description of how and when the problem appears Finding the root cause most difficult step.  key: ...
Read more

Getting started with Git

Best Resources: Git Book from GitHub   Book starts explaining version control, then install, then config and continues as git is used locally, to branches, to uploading to gitHub, and beyond to collabrating. Git Docs Getting git 0)    Check if  git already installed?  From cmd line: git --version   to see if installed  Installed? Skip to 2) 1)  (Ch.1.5) Install Git - by going to Git docs or online book and follow directions for your O/S. 2)  (Ch.1.6)  First-Time Git Setup using git config  set your name, email, and optionally editor and more. Basic git config settings: Identity git config --global user.name "John Doe" git config --global user.email johndoe@example.com Editor git config --global core.editor "'C:/Program Files/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin" (lab1.3) End of Line Preferences git config --global core.autocrlf true git config --global core.safecrlf true Check your settings: ...
Read more