Announcement

Collapse
No announcement yet.

The GNOME Shell Calendar Will Stop Over-Consuming The CPU, Eating Up Battery Life

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • The GNOME Shell Calendar Will Stop Over-Consuming The CPU, Eating Up Battery Life

    Phoronix: The GNOME Shell Calendar Will Stop Over-Consuming The CPU, Eating Up Battery Life

    For the past five months there has been a bug report affecting the likes of Pop OS 19.10 and Fedora 31 over the GNOME Shell Calendar server using "20~25% CPU all the time" and "every 2-3 seconds or so there is a CPU usage spike where the calendar processes eat something like 20-25% of the CPU." That is significant on modern CPUs as well as on battery life for laptops while finally the issue has been fixed...

    http://www.phoronix.com/scan.php?pag...ndar-Power-Fix

  • #2
    Well, that happens if you happen to focus on brainfuck, python and such stuff instead of writing effective code with efficient tools.

    Comment


    • #3
      Originally posted by Brane215 View Post
      Well, that happens if you happen to focus on brainfuck, python and such stuff instead of writing effective code with efficient tools.
      What that has to do with the issue? It was just bad code. No programming language in the world can fix stupid, and in fact, stupid is worse the lower level you go....

      Comment


      • #4
        That’s about the last fix needed..

        Comment


        • #5
          Originally posted by TemplarGR View Post

          What that has to do with the issue? It was just bad code. No programming language in the world can fix stupid, and in fact, stupid is worse the lower level you go....
          Everyone is stupid. Those who think they're not are in for a real treat at some point lol.

          Comment


          • #6
            Originally posted by 144Hz View Post
            That’s about the last fix needed..
            The one where a single process was using over 20% of your cpu all the time? Good thing it only took them 5 months. I mean, any longer than five months and it would almost seem not worth using.

            Comment


            • #7
              Originally posted by Brane215 View Post
              Well, that happens if you happen to focus on brainfuck, python and such stuff instead of writing effective code with efficient tools.
              So, what is your definition of efficient tools and examples of effective code, where this would never happen? Please provide some examples and enlighten us with your wit. Nobody is impressed by your hand waving.

              Comment


              • #8
                Make GNOME great again.
                I once had a dream
                Ich bin ein XFCE User
                Ninety-nine percent of failures come from people who make GNOME
                The only thing we have to fear is GNOME
                Never waste a minute thinking about desktops you don’t like
                Yes we scam

                Comment


                • #9
                  The merge request has a milestone for gnome 3.38. Is it also going into 3.36? It would be a shame to have this issue for the next 6 months..

                  Comment


                  • #10
                    Originally posted by 144Hz View Post
                    That’s about the last fix needed..
                    you don't disappoint man
                    gotta give you that )))))))))))))))))))))))

                    PS gnome sh*t obviously

                    Comment

                    Working...
                    X