الکس چیما و اَش هارت اومدن یه راهکار مشتی برای اجرای بهینهی هوش مصنوعی رو ترکیب سرور و مکبوک رو کردن

الکس چیما و اَش هارت اومدن یه راهکار مشتی برای اجرای بهینهی هوش مصنوعی رو ترکیب سرور و مکبوک رو کردن. ماجرا اینه که مرحلهی پیشپردازش (Prefill) زور پردازشی خالص میخواد و رو سرور DGX Spark با ۳۵۰ ترافلاپس قدرت، حدود ۵ برابر سریعتر از مکبوک M5 Max جلو میره؛ ولی تولید متن یا همون دیکود به پهنای باند رم نیاز داره که مکبوک با سرعت ۶۱۴ گیگابایت بر ثانیه، دو برابر سرور خروجی میده. خلاصه قضیه رو تفکیک کردن تا پیشپردازش روی سرور انجام بشه و دیتای کَش با شبکه ۱۰ گیگابیتی فرستاده بشه رو مکبوک تا کار با بالاترین سرعت تموم بشه. تازه با فناوری RDMA میشه این شبکه رو انقدر سریع کرد که بخشهای سنگین مدل مثل Attention روی حافظه سریعتر و بقیه روی حافظه بزرگتر بشینن.
منبع
Alex Cheema@alexocheema
Excited to collab with @ashxhart on this!
Why does prefill/decode disaggregation work on DGX Spark + Mac ?
DGX Spark: ~350 TFLOPS@fp4, 128GB@273GB/s
M5 Max MacBook Pro: ~70 TFLOPS@fp4, 128GB@614GB/s
Prefill is compute-bound. Prefill on Spark runs ~5x faster than M5 Max.
Decode is memory-bound. Decode on M5 Max runs ~2x faster than Spark.
Simple idea: run prefill on Spark, decode on M5 Max. That's faster than running on one device alone, since each phase runs on the best device for that phase.
This requires sending the KV cache from the Spark to the Mac. With a 10 Gigabit connection, we can overlap fully computation and communication of the KV cache. This doesn't require low latency, and works just fine over TCP/IP.
RDMA on the other hand enables low latency networking (~single digit microseconds), which is the unlock for scaling up decode with ~equal memory bw devices e.g. DGX Spark + M4 Pro / M5 Pro.
Low-latency is also important for DGX Spark + RTX or Mac + RTX. Small pool of very high speed memory + large pool of slower memory is the ideal local hardware architecture. Idea is to put the attention part of the model on the faster small memory pool, and the MoE part on the slower large memory pool.
Ash Hart @ashxhart
MCDMA | Release Update 🚀
After a couple of conversations with @alexocheema, it became clear we’re very aligned on what MCDMA could unlock for local AI and what I’ve been trying to achieve with it.
Alex originally reached out because he’d been following the work and saw a lot of overlap with what @exolabs has been building. Once we started digging in, I got pretty excited about what becomes possible when you combine the two.
So I’ve decided to collaborate with EXO on the next stage of MCDMA.
The goal stays exactly the same. If anything, this just lets us be more ambitious and explore some things that weren’t possible before.
I want to spend a little more time exploring that before sharing the next step.
Genuine thanks to Alex for reaching out and offering support before any collaboration was even on the table. Really looking forward to what we can build together.
More soon.
۲۹ مرداد ۱۴۰۵مشاهده در X
نظرها
هنوز نظری نیست.
بخش نظرها فعلاً در دسترس نیست.