NULL

RELEASE sys-clk under/overclocking sysmodule

Discussion in 'Switch - Emulation, Homebrew & Software Projects' started by m4xw, Feb 14, 2019.

  1. guily6669

    guily6669 GbaTemp is my Drug

    Member
    7
    Jun 3, 2013
    United States
    Doomed Island
    Maybe its using some kind of cuda core acceleration then?

    Here in my PC most games while loading the GPU doesnt even turn the fans on, most of the time it just stay at idle frequencies, 300mhz on the clock and 300 mhz on the memmories (effective 1300mhz since its GDDR5, as soon as the game is running it jumps right away to 8000mhz effectively), but it also depends on the game, most lock the FPS at 30 FPS or 60 while loading for me then unlimited in-game since I never use V-sync or any kind of fps cap on any game unless it comes with it from factory and doesnt allow to change which is very rare.
     
  2. fst312

    fst312 GBAtemp Advanced Fan

    Member
    6
    Nov 4, 2008
    United States
    New York
    I honestly think Nintendo over clocked Zelda after testing the available options that were available after testing sys-clk or freebird. That’s why I think the 8.0 firmware added it in if I read correctly, developers now just need to update their games to take advantage of this.
     
  3. ZachyCatGames

    ZachyCatGames GBAtemp Advanced Maniac

    Member
    8
    Jun 19, 2018
    United States
    Hell
    It was added in 7.0.0, which released before sysclk and freebird
     
  4. chartube12

    chartube12 Captain Chaz 86

    Member
    7
    Mar 3, 2010
    United States
    Not joking
     
  5. [Truth]

    [Truth] GBAtemp Advanced Fan

    Member
    6
    Mar 21, 2006
    Germany
    Mushroom Kingdom
    Is it normal that the clocks are not locked to their value?
    They fluctuate a lot and rarely hit max setting (CPU@1224, GPU@768, MEM@1600, handheld with official charger).
    Games were Doom, BOTW and Snake Pass.
    Code:
    [2019-04-30 13:41:02] [mgr] Console profile changed to: Handheld (Charging: Official)
    [2019-04-30 13:41:15] [mgr] Application TitleID changed to: 0100416004C00000
    [2019-04-30 13:41:16] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:41:16] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:41:16] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:42:25] [mgr] GPU clock is now 384000000
    [2019-04-30 13:42:25] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:42:25] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:42:25] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:42:28] [mgr] GPU clock is now 307200000
    [2019-04-30 13:42:28] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:42:28] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:42:28] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:42:31] [mgr] CPU clock is now 1224000000
    [2019-04-30 13:42:31] [mgr] GPU clock is now 768000000
    [2019-04-30 13:42:31] [mgr] Memory clock is now 1600000000
    [2019-04-30 13:45:05] [mgr] CPU clock is now 1020000000
    [2019-04-30 13:45:05] [mgr] GPU clock is now 460800000
    [2019-04-30 13:45:05] [mgr] Memory clock is now 1331200000
    [2019-04-30 13:45:05] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:45:05] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:45:05] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:46:05] [mgr] GPU clock is now 384000000
    [2019-04-30 13:46:05] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:46:05] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:46:05] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:46:17] [mgr] GPU clock is now 460800000
    [2019-04-30 13:46:17] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:46:17] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:46:17] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:46:20] [mgr] GPU clock is now 384000000
    [2019-04-30 13:46:20] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:46:20] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:46:20] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:46:32] [mgr] GPU clock is now 460800000
    [2019-04-30 13:46:32] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:46:32] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:46:32] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:47:02] [mgr] Application TitleID changed to: 0100000000001000
    [2019-04-30 13:47:02] [mgr] GPU clock is now 307200000
    [2019-04-30 13:47:05] [mgr] Application TitleID changed to: 01007EF00011E000
    [2019-04-30 13:47:05] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:47:05] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:47:05] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:47:08] [mgr] CPU clock is now 1785000000
    [2019-04-30 13:47:08] [mgr] GPU clock is now 76800000
    [2019-04-30 13:47:08] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:47:08] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:47:09] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:47:12] [mgr] CPU clock is now 1224000000
    [2019-04-30 13:47:12] [mgr] GPU clock is now 768000000
    [2019-04-30 13:47:12] [mgr] Memory clock is now 1600000000
    [2019-04-30 13:47:15] [mgr] CPU clock is now 1020000000
    [2019-04-30 13:47:15] [mgr] GPU clock is now 76800000
    [2019-04-30 13:47:15] [mgr] Memory clock is now 1331200000
    [2019-04-30 13:47:15] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:47:15] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:47:15] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:47:18] [mgr] GPU clock is now 460800000
    [2019-04-30 13:47:18] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:47:18] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:47:18] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:47:21] [mgr] CPU clock is now 1224000000
    [2019-04-30 13:47:21] [mgr] GPU clock is now 768000000
    [2019-04-30 13:47:21] [mgr] Memory clock is now 1600000000
    [2019-04-30 13:48:36] [mgr] CPU clock is now 1785000000
    [2019-04-30 13:48:36] [mgr] GPU clock is now 76800000
    [2019-04-30 13:48:36] [mgr] Memory clock is now 1331200000
    [2019-04-30 13:48:36] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:48:36] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:48:36] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:48:39] [mgr] CPU clock is now 1224000000
    [2019-04-30 13:48:39] [mgr] GPU clock is now 768000000
    [2019-04-30 13:48:39] [mgr] Memory clock is now 1600000000
    [2019-04-30 13:48:51] [mgr] CPU clock is now 1020000000
    [2019-04-30 13:48:51] [mgr] GPU clock is now 460800000
    [2019-04-30 13:48:51] [mgr] Memory clock is now 1331200000
    [2019-04-30 13:48:51] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:48:51] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:48:51] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:51:03] [mgr] Application TitleID changed to: 0100000000001000
    [2019-04-30 13:51:05] [mgr] GPU clock is now 307200000
    [2019-04-30 13:51:08] [mgr] Application TitleID changed to: 0100C0F0020E8000
    [2019-04-30 13:51:08] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:51:08] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:51:08] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:51:11] [mgr] GPU clock is now 384000000
    [2019-04-30 13:51:11] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:51:11] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:51:11] [mgr] Setting Memory clock to 1600000000
    [2019-04-30 13:51:14] [mgr] CPU clock is now 1224000000
    [2019-04-30 13:51:14] [mgr] GPU clock is now 768000000
    [2019-04-30 13:51:14] [mgr] Memory clock is now 1600000000
    [2019-04-30 13:52:47] [mgr] CPU clock is now 1020000000
    [2019-04-30 13:52:47] [mgr] GPU clock is now 384000000
    [2019-04-30 13:52:47] [mgr] Memory clock is now 1331200000
    [2019-04-30 13:52:47] [mgr] Setting CPU clock to 1224000000
    [2019-04-30 13:52:47] [mgr] Setting GPU clock to 768000000
    [2019-04-30 13:52:47] [mgr] Setting Memory clock to 1600000000
    
     
  6. OrGoN3

    OrGoN3 GBAtemp Addict

    Member
    8
    Apr 23, 2007
    United States
    Does using this interfere with the 'Boost Mode' in 8.x.x? Does sys-clk override the values thus making boost mode pointless?
     
  7. Brawl345

    Brawl345 GBAtemp Advanced Fan

    Member
    8
    Jan 14, 2012
    Germany
     
  8. stick267

    stick267 GBAtemp Fan

    Member
    4
    Dec 17, 2018
    United States
    Well, the Boost Mode is only temporary during load screens. You can set sys-clk and it'll be persistent the whole time for actual gameplay.
     
  9. ZachyCatGames

    ZachyCatGames GBAtemp Advanced Maniac

    Member
    8
    Jun 19, 2018
    United States
    Hell
    having the cpu any higher than normal is pointless during regular gameplay in botw and Mario Odyssey though
     
    stick267 likes this.
  10. Zap Rowsdower

    Zap Rowsdower I am you.

    Member
    5
    Jan 17, 2015
    Canada
    I don't go map findin' behindin'
    Especially where stereoscopic 3D mode hits performance, I think the default sys-clk config sets for constant 1224000000 in addition to the RAM docked clock is very much worth it. After the loading screen boost it looks like it goes right back to that config.
     
  11. renatosk

    renatosk Advanced Member

    Newcomer
    3
    Jan 11, 2016
    Brazil
    sys-clk got featured on a digital foundry video!
     
  12. JHumBL3

    JHumBL3 Member

    Newcomer
    2
    Nov 22, 2018
    United States
    Does this only work for Atmosphere and ReiNX?
     
  13. hippy dave

    hippy dave BBMB

    Member
    14
    Apr 30, 2012
    United Kingdom
    Yes, sx os doesn't allow custom sysmodules.
     
    JHumBL3 and Mouser X like this.
  14. [Truth]

    [Truth] GBAtemp Advanced Fan

    Member
    6
    Mar 21, 2006
    Germany
    Mushroom Kingdom
    FYI, I tested with the FW 8+ beta release of Freebird (get it here) and the clocks are locked there.
    Played a bit of BotW and in Korok Forest the OC was immediately noticable.
    I think there might be a bug in sys-clk?
     
  15. p-sam

    p-sam Member

    Newcomer
    2
    Feb 3, 2019
    France
    Logs tells you the games are periodically adjusting profiles (and it's known that DOOM does that a lot, BOTW does too), and sys-clk then applies back your custom frequencies each time.
     
  16. Jackson98

    Jackson98 GBAtemp Regular

    Member
    3
    Aug 8, 2017
    Australia
    Is overclocking more of a risk on more intensive games? Or is the fact your overclocking a risk factor in general?
    For E.G if you are using overclocking to increase retro game performance for Gamecube titles, running at the same clock speeds would you run higher risks overclocking Skryim?
    Or for a better insight, If I ran Skyrim with regular clock speeds intended by Nintendo, would it still take more of a toll OCing less damanding games??
     
  17. [Truth]

    [Truth] GBAtemp Advanced Fan

    Member
    6
    Mar 21, 2006
    Germany
    Mushroom Kingdom
    I thought so too, but i.e. the stuttering in Korok Forest didn´t go away with sys-clk OC on fw 8+, whereas with Freebird it´s completely smooth.
    The only risk imo is the increased strain on the battery.
    Thats why I only do it with the charger plugged in, but then I run max clock speeds without problems.
    The Switch doesn´t even get hot, the cooler looks like it can handle it easily.
    Anyone who ever had a reference design PC GPU with blower style cooling knows how these things can operate.
     
    Last edited by [Truth], May 12, 2019
    Jackson98 likes this.
  18. p-sam

    p-sam Member

    Newcomer
    2
    Feb 3, 2019
    France
    Those are 2 completely different things, the game is surely setting its clocks back. And judging on how verbose your log is, it may very well be instantly after. I would prefer to avoid having clocks being switched every instant, and the current polling interval is 3s. Wanna try with a 100ms polling interval ? I've been playing with it for a while like this. There's currently a beta of this being tested on our discord server.
     
    Last edited by p-sam, May 13, 2019
    [Truth] likes this.
  19. pcwizard7

    pcwizard7 GBAtemp Regular

    Member
    3
    Aug 2, 2013
    Australia
    can you set a global settings for system wide?

    thanks
     
    Last edited by pcwizard7, May 15, 2019
  20. m4xw
    OP

    m4xw Ancient Deity

    Member
    15
    May 25, 2018
    Germany
    No, we specifically don't want people to do that, but rather let them tweak each title individually.
    However, with addition of the GUI, it will be possible, but implementation wise its different.
     
    p-sam likes this.
Loading...