A model too large for one phone? Acurast wants a fleet of phones to run it
Phone computing has one unavoidable limitation: there’s only so much memory. Some models simply won’t fit on a single device.
In its official article on October 14, @Acurast once again mentioned its Cray compute cluster plan. The goal is to organize hundreds of devices to ease the computing constraints of individual phones and take on larger model workloads.
There’s an important distinction to make here.
Having many phones each handle small tasks is very different from having multiple phones work together on one larger task. Cray is targeting the latter. The official roadmap also lists it separately as Compute Clusters.
If this works, developers may have a wider range of workloads to choose from. Phone owners’ devices could also take part in tasks that a single device couldn’t handle.
Cray is still a planned capability. The latest official article discusses the goal; it shouldn’t be described as a product that’s already widely available.
I’m optimistic about this direction, and I hope the upcoming demonstrations are concrete.
Take a model that genuinely can’t run on one phone, and disclose how many devices it needs, how long it takes, and what each call costs. With those numbers out in the open, developers can judge whether their applications are a good fit.
The question Acurast is trying to answer is: just how much work can phone computing take on?
#Acurast #AI #DePIN
Phone computing has one unavoidable limitation: there’s only so much memory. Some models simply won’t fit on a single device.
In its official article on October 14, @Acurast once again mentioned its Cray compute cluster plan. The goal is to organize hundreds of devices to ease the computing constraints of individual phones and take on larger model workloads.
There’s an important distinction to make here.
Having many phones each handle small tasks is very different from having multiple phones work together on one larger task. Cray is targeting the latter. The official roadmap also lists it separately as Compute Clusters.
If this works, developers may have a wider range of workloads to choose from. Phone owners’ devices could also take part in tasks that a single device couldn’t handle.
Cray is still a planned capability. The latest official article discusses the goal; it shouldn’t be described as a product that’s already widely available.
I’m optimistic about this direction, and I hope the upcoming demonstrations are concrete.
Take a model that genuinely can’t run on one phone, and disclose how many devices it needs, how long it takes, and what each call costs. With those numbers out in the open, developers can judge whether their applications are a good fit.
The question Acurast is trying to answer is: just how much work can phone computing take on?
#Acurast #AI #DePIN
