4 ms·

I know it's probably really early to ask this, but do you have a rough estimate of when the power usage improvements will happen? Battery life is the main thing

by 43920 8y ago

I know it's probably really early to ask this, but do you have a rough estimate of when the power usage improvements will happen? Battery life is the main thing stopping me from using Firefox more, so I'm really looking forward to this being fixed.

agumonkey 8y ago
I had a ~power related issue using Quantum. It "killed" my cpu (temp rising by 10s of degrees so fast I didn't have time to throttle before kernel thermal shutdown). I guess it's so parallel and so gpu intensive that my whole system goes into fever. ps: a x201 core i5 520m
- mort96 8y ago
  What? Your system doesn't handle running at max CPU and GPU usahe even for what I presume is seconds before thermal shutdown? That seems like an extremely serious issue with your system.
  - agumonkey 8y ago
    All I can tell is that ffx quantum is the only program that triggers that behavior. And it's not seconds it's maybe one second. 70-80-90 off.
    - deleted 8y ago
      [deleted]
    - zymhan 8y ago
      Run Prime95 on torture mode and then tell me it's just Firefox. Because what you've said makes no sense.
      - agumonkey 8y ago
        I don't care a single second what you think about what I said.
- DiabloD3 8y ago
  Clean your heatsink out, and also consider replacing the heatsink paste: that CPU is so old, its entirely possible a cheap thermal pad is no longer usable (commonly used on laptops and stock desktop HSFs).
  - agumonkey 8y ago
    Doesn't matter, I burn the cpu with multiple gcc builds and it doesn't rise the same. I had thermal shutdowns it can happen, but not like ffx quantum.
    - pcwalton 8y ago
      I'm going to guess your problem is not CPU related, but rather a hardware issue relating to other hardware that Firefox uses (GPU, audio, …) Firefox spends most of its time idling in event loops; it's not a batch job like a compiler.
      - agumonkey 8y ago
        Note that I'm not blaming ffx, just witnessing something weird and wondering if it's due to using rust parallelism in ways not done through the usual cpp libs.
        pcwalton 8y ago
        Very doubtful. The only thing I could think of that might conceivably cause similar symptoms would be AVX2, but none of our shipping Rust code uses that.
        agumonkey 8y ago
        Odd then. I wasn't even using a specific webpage, just loading the previous session (~20tabs of average intensiveness). Chromium has the same kind of session and it never causes similar heat spikes. Anyway I'll try to reproduce it even though it's not pleasing to overheat like that.

by 43920 8y ago

agumonkey 8y ago

I had a ~power related issue using Quantum. It "killed" my cpu (temp rising by 10s of degrees so fast I didn't have time to throttle before kernel thermal shutdown). I guess it's so parallel and so gpu intensive that my whole system goes into fever. ps: a x201 core i5 520m

mort96 8y ago
What? Your system doesn't handle running at max CPU and GPU usahe even for what I presume is seconds before thermal shutdown? That seems like an extremely serious issue with your system.
- agumonkey 8y ago
  All I can tell is that ffx quantum is the only program that triggers that behavior. And it's not seconds it's maybe one second. 70-80-90 off.
  - deleted 8y ago
    [deleted]
  - zymhan 8y ago
    Run Prime95 on torture mode and then tell me it's just Firefox. Because what you've said makes no sense.
    - agumonkey 8y ago
      I don't care a single second what you think about what I said.
DiabloD3 8y ago
Clean your heatsink out, and also consider replacing the heatsink paste: that CPU is so old, its entirely possible a cheap thermal pad is no longer usable (commonly used on laptops and stock desktop HSFs).
- agumonkey 8y ago
  Doesn't matter, I burn the cpu with multiple gcc builds and it doesn't rise the same. I had thermal shutdowns it can happen, but not like ffx quantum.
  - pcwalton 8y ago
    I'm going to guess your problem is not CPU related, but rather a hardware issue relating to other hardware that Firefox uses (GPU, audio, …) Firefox spends most of its time idling in event loops; it's not a batch job like a compiler.
    - agumonkey 8y ago
      Note that I'm not blaming ffx, just witnessing something weird and wondering if it's due to using rust parallelism in ways not done through the usual cpp libs.
      - pcwalton 8y ago
        Very doubtful. The only thing I could think of that might conceivably cause similar symptoms would be AVX2, but none of our shipping Rust code uses that.
        agumonkey 8y ago
        Odd then. I wasn't even using a specific webpage, just loading the previous session (~20tabs of average intensiveness). Chromium has the same kind of session and it never causes similar heat spikes. Anyway I'll try to reproduce it even though it's not pleasing to overheat like that.