็™ป้Œฒใ—ใฆๆ‹›ๅพ…ใƒชใƒณใ‚ฏใ‚’ๅ…ฑๆœ‰ใ™ใ‚‹ใจใ€ๅ‹•็”ปๅ†็”Ÿๅ ฑ้…ฌใจ็ดนไป‹ๅ ฑ้…ฌใ‚’็ฒๅพ—ใงใใพใ™ใ€‚

David Hendrickson
@TeksEdge
CEO & Founder | PhD | Startup Advisor | @Columbia | Author Generative Software Engineering | ๐Ÿ”” Follow for AI & Vibe Coding Tips ๐Ÿ‘‡
ๅ‚ๅŠ  July 2023
552 ใƒ•ใ‚ฉใƒญใƒผไธญ    12.5K ใƒ•ใ‚กใƒณ
This new-ish 35B multimodal model went from 3.38 โ†’ 20.51 tps on an iPhone. MiniCPM-V 4.7 35B-A3B was updated to decode faster on the iPhone by improving how it moves the model between storage and memory. Constraints ๐Ÿง  35B total / ~3B active ๐Ÿ“ฑ iPhone 18 Pro Max โ€” 12GB RAM ๐Ÿ‘๏ธ image + multi-image + video understanding Most of those 35B weights don't sit in RAM. The experts can stay in the phone's flash storage and get loaded when they're actually needed. Normally that's slow ๐ŸŒ SSD expert loading โ†’ 3.38 t/s So OpenBMB built Lookahead Expert Scheduling (LES) It predicts which experts the next layer will probably need and starts loading them while the current layer is still computing. Then they stacked the optimizations: ๐Ÿ’พ baseline SSD loading โ†’ 3.38 tps ๐Ÿ‘€ expert lookahead โ†’ 6.57 โš™๏ธ optimized scheduling/loading โ†’ 11.34 ๐Ÿ—œ๏ธ mixed-precision quantization โ†’ 17.16 ๐Ÿš€ + DSpark speculative decoding โ†’ 20.51 tps That's a 6.07ร— speedup over the same-phone unoptimized baseline. โš ๏ธ And these are still OpenBMB's own measurements. Link in ALT
ใ‚‚ใฃใจ่ฆ‹ใ‚‹