Rediculous !

Discussion in 'other software & services' started by rrrh1, Oct 10, 2015.

  1. rrrh1

    rrrh1 Registered Member

    Joined:
    Sep 10, 2007
    Posts:
    202
    Browser 1 uses 20% CPU and 1.1 Gb of RAM to display 1 webpage. Ridiculous !

    Browser 2 uses 1% CPU and 200Mb of Ram to display 2 tabs
    the one that is currently open is the same webpage as above.

    I have been told I am obsessing over nothing.

    I think of it like this, browser 1 is like a car that gets 5 miles to the gallon, and browser
    2 like a car that gets 25 miles to the gallon.

    You can open a lot (about 5x) more websites before you run out of gasoline (RAM) with browser 2.

    rrrh1
     
  2. amarildojr

    amarildojr Registered Member

    Joined:
    Aug 8, 2013
    Posts:
    1,985
    Location:
    Brasil
    Let me guess: browser one is Chrome? :p

    1 GB is a lot for a single webpage, unless this webpage is a 1-hour youtube video that is being displayed in 4k :cool:
     
  3. J_L

    J_L Registered Member

    Joined:
    Nov 6, 2009
    Posts:
    8,516
    Browser, OS, etc.? Or are we shooting in the dark?
     
    Last edited: Oct 10, 2015
  4. DOSawaits

    DOSawaits Registered Member

    Joined:
    Dec 11, 2008
    Posts:
    416
    Location:
    Belgium
    My guess is that browser 1 is Firefox & browser 2 is IE.
     
  5. allizomeniz

    allizomeniz Registered Member

    Joined:
    Aug 23, 2009
    Posts:
    904
    I wouldn't be surprised if 1 is Firefox. It's getting to be a ridiculous resource hog.
     
  6. anon

    anon Registered Member

    Joined:
    Dec 27, 2012
    Posts:
    4,095
    The thread [title] is ridiculous.
     
  7. Rolo42

    Rolo42 Registered Member

    Joined:
    Jan 22, 2012
    Posts:
    569
    Location:
    USA
    Not if it's Chrome and you have apps and extensions running vs Edge which doesn't do much of anything besides displaying a web page. Without details, I'm afraid you may be jumping to conclusions.
     
  8. TairikuOkami

    TairikuOkami Registered Member

    Joined:
    Oct 10, 2005
    Posts:
    2,509
    Location:
    Slovakia
    Indeed, that is why Cleanmem was designed and solves memory hogs due to Windows 10's bad memory management as well.
     
  9. Rolo42

    Rolo42 Registered Member

    Joined:
    Jan 22, 2012
    Posts:
    569
    Location:
    USA
    It is bad, precisely, how?
     
  10. TairikuOkami

    TairikuOkami Registered Member

    Joined:
    Oct 10, 2005
    Posts:
    2,509
    Location:
    Slovakia
    Because they refuse to fix it stating, that it is superfetch and other nonsense and people just do understand, how memory management works, a typical PR response. Yet people fixed their memory issues using Cleanmem, issues which involved crashing and lagging due to high memory usage.
     
  11. Rolo42

    Rolo42 Registered Member

    Joined:
    Jan 22, 2012
    Posts:
    569
    Location:
    USA
    Fix, exactly, what? What is wrong with it?
     
  12. TairikuOkami

    TairikuOkami Registered Member

    Joined:
    Oct 10, 2005
    Posts:
    2,509
    Location:
    Slovakia
    I am not a programmer, can not explain it in detail, but simply put, Windows should release an unused pre-cached memory, when other app needs it, but it fails to do so, that is where Cleanmem comes, it just asks Windows to do it and it does. Some part of code is messed up there since Vista.
     
  13. Rolo42

    Rolo42 Registered Member

    Joined:
    Jan 22, 2012
    Posts:
    569
    Location:
    USA
    I only hear this from folks who do one or more of the following:
    • Don't read memory metrics properly
    • Run incompatible software on systems that don't meet minimum requirements and blame Windows
    • Run broken software and blame Windows
    • Write these programs claiming to fix Windows
    I neither deny nor confirm that this gimmick could serve as a workaround in the aforementioned situations, but I have to raise the flag on the statement that Windows doesn't know how to manage memory--which they've improved heavily in 10.