So if we assume this is the future, the useful life of many semiconductors will fall substantially. What part of the semiconductor supply chain would have pricing power in a world of producing many more different designs? Perhaps mask manufacturers?
It might be not that bad. “Good enough” open-weight models are almost there, the focus may shift to agentic workflows and effective prompting. The lifecycle of a model chip will be comparable to smartphones, getting longer and longer, with orchestration software being responsible for faster innovation cycles.
How Taalas “prints” LLM onto a chip?
71–80 of 266 posts
Re: How Taalas “prints” LLM onto a chip?
#72Who's going to pay for custom chips when they shit out new models every two weeks and their deluded CEOs keep promising AGI in two release cycles?
You obviously don't believe that AGI is coming in two release cycles, and you also don't seem to have much faith in the new models containing massive improvements over the last ones. So the answer to who is going to pay for these custom chips seems to be you.
Re: How Taalas “prints” LLM onto a chip?
#73Earlier quoted context omitted.
Pretty sure it'd just be a thumbdrive. Are the Taalas chips particularly large in surface area?
The only product they've announced at the moment [0] is a PCI-e card. It's more like a small power bank than a big thumb drive. But sure, the next generation could be much smaller. It doesn't require battery cells, (much) heat management, or ruggedization, all of which put hard limits on how much you can miniaturise power banks. [0] https://taalas.com/the-path-to-ubiquitous-ai/
Nowadays, your average cellphone has more computing power than those behemoths.
I have a micro SD card with 256GB capacity, and I think they are up to 2TB. On a device the size of a fingernail.
Re: How Taalas “prints” LLM onto a chip?
#74Who's going to pay for custom chips when they shit out new models every two weeks and their deluded CEOs keep promising AGI in two release cycles?
Re: How Taalas “prints” LLM onto a chip?
#75Earlier quoted context omitted.
New GPUs come out all the time. New phones come out (if you count all the manufacturers) all the time. We do not need to always buy the new one. Current open weight models < 20B are already capable of being useful. With even 1K tokens/second, they would change what it means to interact with them or for models to interact with the computer.
hm yeah I guess if they stick to shitty models it works out, I was talking about the models people use to actually do things instead of shitposting from openclaw and getting reminders about their next dentist appointment.
Re: How Taalas “prints” LLM onto a chip?
#76Earlier quoted context omitted.
That slot is called USB-C. I can fully imagine inference ASICs coming in powerbank form factor that you'd just plug and play.
Not if you need 200w power to run inference.
Re: How Taalas “prints” LLM onto a chip?
#77>HOW NVIDIA GPUs process stuff? (Inefficiency 101) Wow. Massively ignorant take. A modern GPUs is an amazing feat of engineering, particularly about making computation more efficient (low power/high throughput). Then proceeds to explain, wrongly, how inference is supposssedly implemented and draws conclusions from there ...
Re: How Taalas “prints” LLM onto a chip?
#78Re: How Taalas “prints” LLM onto a chip?
#79> Kinda like a CD-ROM/Game cartridge, or a printed book, it only holds one model and cannot be rewritten. Imagine a slot on your computer where you physically pop out and replace the chip with different models, sort of like a Nintendo DS.
That slot is called USB-C. I can fully imagine inference ASICs coming in powerbank form factor that you'd just plug and play.
With these speeds you can run it over USB2, though maybe power is limiting.
Re: How Taalas “prints” LLM onto a chip?
#80So why only 30,000 tokens per second? If the chip is designed as the article says, they should be able to do 1 token per clock cycle... And whilst I'm sure the propagation time is long through all that logic, it should still be able to do tens of millions of tokens per second...
You still need to do a forward pass per token. With massive batching and full pipelining you might be able to break the dependencies and output one token per cycle but clearly they aren't doing that.