mirror of
https://github.com/supabase/supabase.git
synced 2026-05-07 01:10:15 -04:00
Beng Eu
b3dc867f90
Proposed mitigation, the obvious tradeoff is that clearing the cache will make compilation slower on subsequent dev server starts, but more consistent. Various people have been observing `next-server` use up to ~34 GB memory. I've observed 12.59 GB memory, with ~1.5k `postcss` processes: ``` ps aux | grep postcss | grep -v grep | wc -l 1526 ``` Going down to 3 `postcss` process and 4.71 GB memory after clearing cache: ``` ps aux | grep postcss | grep -v grep | wc -l 3 ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Development infrastructure: adds an automated pre-development step that clears the local dev cache before starting the development server by introducing a new lifecycle hook and supporting cleanup script; purely maintenance-oriented with no user-facing changes or functional impact. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>