While running deepseek-v4-pro with the latest commit (477c0e8 at the time of writing) on a single 512GB Mac Studio, generation was so slow it was basically unusable. Watching mactop, it looked like memory was rapidly allocating/deallocating with high CPU usage observed on the ds4-server process too.
Reverting to the commit prior to 3c3ad4c returned things to normal.
Temporary workaround for anyone else experiencing this:
git checkout ba00a8a88c4c5810a3d1fed6b7b8fa2b44b82fdcmake cleanmake
While running deepseek-v4-pro with the latest commit (477c0e8 at the time of writing) on a single 512GB Mac Studio, generation was so slow it was basically unusable. Watching
mactop, it looked like memory was rapidly allocating/deallocating with high CPU usage observed on theds4-serverprocess too.Reverting to the commit prior to 3c3ad4c returned things to normal.
Temporary workaround for anyone else experiencing this:
git checkout ba00a8a88c4c5810a3d1fed6b7b8fa2b44b82fdcmake cleanmake