You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As somewhat described in IntersectMBO/cardano-node#5500, I saw time from Daedalus startup to full functionality on the order of 4+ hours, further exacerbated by frequent disconnections from mainnet, necessitating a restart of cardano-node.
Jumping through some hacky hoops, I managed to pass on other Haskell RTS options than the ones I since learned where offered in the GUI for low-memory systems, to discover not only how to utilise more than one core, but that this had the following effects:
Start-up to full functionality is now on the order of 10 - 20 minutes as opposed to 4+ hours
Whereas earlier, Daedalus would lose connection to mainnet on a daily basis, I haven't seen that for a few days now
Wading through the quagmires of a compiled Nix package was dreary, so I shall not be making PR, but I would propose to implement a way for the user to specify arbitrary RTS options, as well as to provide reasonable defaults (still overridable), depending on CPU core count.
The text was updated successfully, but these errors were encountered:
Opting for another approach than just specifying +RTS -N -RTS which would utilise all available CPU cores, I opted for half the amount of physical cores in my machine with +RTS -N14 -RTS.
Since then, I lowered that to +RTS -N8 -RTS to utilize only 8 cores, and realising that some people, myself included, would very much like to not have any single program utilise all cores "nilly-willy", my suggestion is to apply some heuristic such as, say, half or a quarter of available physical or logical cores, but then let the user alter those parameters at will.
As somewhat described in IntersectMBO/cardano-node#5500, I saw time from Daedalus startup to full functionality on the order of 4+ hours, further exacerbated by frequent disconnections from mainnet, necessitating a restart of cardano-node.
Jumping through some hacky hoops, I managed to pass on other Haskell RTS options than the ones I since learned where offered in the GUI for low-memory systems, to discover not only how to utilise more than one core, but that this had the following effects:
Wading through the quagmires of a compiled Nix package was dreary, so I shall not be making PR, but I would propose to implement a way for the user to specify arbitrary RTS options, as well as to provide reasonable defaults (still overridable), depending on CPU core count.
The text was updated successfully, but these errors were encountered: