Performance - Netlify deploy and building issues with too many mdEnhance options active

[JeremieLitzler]

Hello @Mister-Hope,

Let's say one has a repo with a few hundreds of markdown files and many of your mdEnhance options are active.

What would you recommend to keep the build time and the JavaScript ressources it uses to acceptable limits?

Here is an extract of a failed build. To solve it, I disable all the mdEnhance I wouldn't use on the site.

11:35:12 AM: Pages generated by Vite =>  346
11:35:13 AM: ✔ Initializing and preparing data - done in 12.06s
11:35:13 AM: - Compiling with vite
11:36:02 AM: <--- Last few GCs --->
11:36:02 AM: [1421:0x5a60c80]    62441 ms: Mark-sweep (reduce) 2031.8 (2079.3) -> 2031.6 (2079.8) MB, 762.0 / 0.0 ms  (+ 44.2 ms in 10 steps since start of marking, biggest step 6.7 ms, walltime since start of marking 818 ms) (average mu = 0.284, current mu = 0.182) a[1421:0x5a60c80]    63275 ms: Mark-sweep (reduce) 2033.7 (2081.3) -> 2033.5 (2081.5) MB, 698.5 / 0.0 ms  (average mu = 0.232, current mu = 0.162) allocation failure GC in old space requested
11:36:02 AM: <--- JS stacktrace --->
11:36:02 AM: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
11:36:02 AM:  1: 0xb08e80 node::Abort() [node]
11:36:02 AM:  2: 0xa1b70e  [node]
11:36:02 AM:  3: 0xce1890 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
11:36:02 AM:  4: 0xce1c37 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
11:36:02 AM:  5: 0xe992a5  [node]
11:36:02 AM:  6: 0xea8f6d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
11:36:02 AM:  7: 0xeabc6e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
11:36:02 AM:  8: 0xe6d1aa v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
11:36:02 AM:  9: 0x11e60cc v8::internal::Runtime_AllocateInOldGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
11:36:02 AM: 10: 0x15d9c19  [node]
11:36:03 AM: Aborted (core dumped)

Thanks.

PS : the site is a private one because it is linked to my company and I cannot share a public version.

[Mister-Hope]

You may manually update old space by updating env variables. Note: This size can be larger then actual mermory size.

A related link: https://stackoverflow.com/questions/56982005/where-do-i-set-node-options-max-old-space-size-2048#:~:text=The%20NODE_OPTIONS%20--max-old-space-size%20environment%20variable%20allows%20to%20increase,and%20can%20be%20utilized%20by%20every%20Node%20process.

[JeremieLitzler]

Thanks @Mister-Hope. Always helpful.