From a9b4fe296011ad2b346ae990e464f9373b6e48ee Mon Sep 17 00:00:00 2001 From: Henrik Lissner Date: Wed, 19 Sep 2018 18:14:01 -0400 Subject: [PATCH] Hard code gc-cons-threshold in early-init.el In the interest of DRY-ness, I avoid redefining `doom-gc-cons-upper-limit`. This value is likely to diverge from the default value of `doom-gc-cons-upper-limit` in the future anyway. --- early-init.el | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/early-init.el b/early-init.el index 8beec8fb5..6d883882a 100644 --- a/early-init.el +++ b/early-init.el @@ -3,11 +3,8 @@ ;; Emacs HEAD (27+) introduces early-init.el, which is run before init.el, ;; before package and UI initialization happens. - -(defconst doom-gc-cons-upper-limit 268435456 ; 256mb - "The temporary value for `gc-cons-threshold' to defer it.") -;; This reduces gcs-done from 4 to 1 on startup -(setq gc-cons-threshold doom-gc-cons-upper-limit) +;; Defer garbage collection further back in the startup process +(setq gc-cons-threshold 268435456) ;; Package initialize occurs automatically, before `user-init-file' is ;; loaded, but after `early-init-file'. Doom handles package