| ▲ | alyxya a day ago |
| The hardest part about making a new architecture is that even if it is just better than transformers in every way, it’s very difficult to both prove a significant improvement at scale and gain traction. Until google puts in a lot of resources into training a scaled up version of this architecture, I believe there’s plenty of low hanging fruit with improving existing architectures such that it’ll always take the back seat. |
|
| ▲ | p1esk a day ago | parent | next [-] |
| Until google puts in a lot of resources into training a scaled up version of this architecture If Google is not willing to scale it up, then why would anyone else? |
| |
| ▲ | 8note a day ago | parent [-] | | chatgpt is an example on why. | | |
| ▲ | falcor84 10 hours ago | parent [-] | | You think that this might be another ChatGPT/Docker/Hadoop case, where Google comes up with the technology but doesn't care to productize it? |
|
|
|
| ▲ | tyre a day ago | parent | prev | next [-] |
| Google is large enough, well-funded enough, and the opportunity is great enough to run experiments. You don't necessarily have to prove it out on large foundation models first. Can it beat out a 32b parameter model, for example? |
| |
| ▲ | swatcoder a day ago | parent [-] | | Do you think there might be an approval process to navigate when experiments costs might run seven or eight digits and months of reserved resources? While they do have lots of money and many people, they don't have infinite money and specifically only have so much hot infrastructure to spread around. You'd expect they have to gradually build up the case that a large scale experiment is likely enough to yield a big enough advantage over what's already claiming those resources. | | |
| ▲ | dpe82 17 hours ago | parent | next [-] | | I would imagine they do not want their researchers unnecessarily wasting time fighting for resources - within reason. And at Google, "within reason" can be pretty big. | | |
| ▲ | howdareme 15 hours ago | parent [-] | | I mean looking antigravity, jules & gemini cli, they have have no problem with their developers fighting for resources |
| |
| ▲ | nl 14 hours ago | parent | prev [-] | | I mean you'd think so, but... > In fact, the UL2 20B model (at Google) was trained by leaving the job running accidentally for a month. https://www.yitay.net/blog/training-great-llms-entirely-from... |
|
|
|
| ▲ | m101 a day ago | parent | prev | next [-] |
| Prove it beats models of different architectures trained under identical limited resources? |
|
| ▲ | nickpsecurity a day ago | parent | prev | next [-] |
| But, it's companies like Google that made tools like Jax and TPU's saying we can throw together models with cheap, easy scaling. Their paper's math is probably harder to put together than an alpha-level prototype which they need anyway. So, I think they could default on doing it for small demonstrators. |
|
| ▲ | UltraSane a day ago | parent | prev [-] |
| Yes. The path dependence for current attention based LLMs is enormous. |
| |
| ▲ | patapong a day ago | parent [-] | | At the same time, there is now a ton of data for training models to act as useful assistants, and benchmarks to compare different assistant models. The wide availability and ease of obtaining new RLHF training data will make it more feasible to build models on new architectures I think. |
|