identifying 'heavy' programs

Discussion in 'other software & services' started by mr mister, Oct 16, 2008.

Thread Status:
Not open for further replies.
  1. mr mister

    mr mister Registered Member

    Joined:
    Nov 27, 2007
    Posts:
    47
    i am looking for a program to tell me the amount of resources that various programs are consuming
    sometimes my computers gets very slow,so i want to find the culprit program/s
    i want to try and get rid of programs which are too heavy or swap them with lighter alternatives,but first i have to identify these heavy programs
    how do i do this?

    thank you.
     
  2. bigc73542

    bigc73542 Retired Moderator

    Joined:
    Sep 21, 2003
    Posts:
    23,791
    Location:
    SW. Oklahoma
    which OS are you running??
     
  3. mr mister

    mr mister Registered Member

    Joined:
    Nov 27, 2007
    Posts:
    47
    windows xp
     
  4. bigc73542

    bigc73542 Retired Moderator

    Joined:
    Sep 21, 2003
    Posts:
    23,791
    Location:
    SW. Oklahoma
    I was hoping it was Vista. It has been long enough since I have used XP I actually don't remember exactlly how to get to the app to see the resource usage. Vista is easy but I will have to think a bit and will post back.
     
  5. HURST

    HURST Registered Member

    Joined:
    Jul 20, 2007
    Posts:
    1,419
    I think Tune-Up Utilities has a module to find memory and space hogs.
    There must be other programs as well.
     
  6. PROROOTECT

    PROROOTECT Registered Member

    Joined:
    May 5, 2008
    Posts:
    1,102
    Location:
    HERE ...Fort Lee, NJ
    Last edited: Oct 16, 2008
  7. Seer

    Seer Registered Member

    Joined:
    Feb 12, 2007
    Posts:
    1,596
    Location:
    Singidunum
    Guys,

    am I missing something? What's wrong with the native Task Manager?

    If you want something more comprehensive, then Process Explorer will do the job.

    Opened Files View, NTFSRatio and such will tell you nohing on resources...
     
  8. JRViejo

    JRViejo Global Moderator

    Joined:
    Jul 9, 2008
    Posts:
    16,510
    Location:
    U.S.A.
    I agree with Seer and I would add to insure that Peak Memory Usage is selected via Task Manager's View > Select Columns so that it appears on the Processes window. That column is critical in finding out who's the memory hog.
     
  9. MrBrian

    MrBrian Registered Member

    Joined:
    Feb 24, 2008
    Posts:
    6,032
    Location:
    USA
  10. farmerlee

    farmerlee Registered Member

    Joined:
    Jul 1, 2006
    Posts:
    2,585
    The default taskmanager should be fine. Just go to the 'processes' column then click on 'view' then 'select columns' and you can view whatever info you need.
     
  11. lodore

    lodore Registered Member

    Joined:
    Jun 22, 2006
    Posts:
    8,952
    process explorer,task manager or windows powershell.
    in windows power shell use get-process for all processes
    or for just one process type the get-process (insert process here) or use a wild card such as w* or *w
     
  12. Baldrick

    Baldrick Registered Member

    Joined:
    May 11, 2002
    Posts:
    2,091
    Location:
    South Wales, UK
    Process Explorer without a doubt. Used it in just such a case and it did the trick, ie, identified the culprits.:D
     
  13. bellgamin

    bellgamin Very Frequent Poster

    Joined:
    Aug 1, 2002
    Posts:
    5,447
    Location:
    Hawaii
    Agree totally. Process Explorer is superb -- small, stable, efficient, secure -- plus it is developed & issued by Mark Russinovich in conjunction with a subsidiary-domain of MS itself.

    IMO, one should be very cautious about allowing free access to your hard drives by applications such as those mentioned in post #6.
     
  14. PROROOTECT

    PROROOTECT Registered Member

    Joined:
    May 5, 2008
    Posts:
    1,102
    Location:
    HERE ...Fort Lee, NJ
    Hello Bellgamin,

    WHY is your comment on the applications of post #6:rolleyes: ?

    Thank you for your answer ...:cool:
     
Thread Status:
Not open for further replies.