Live data from Hacker News

OpenAI's plans according to Sam Altman

web.archive.org

51–60 of 70 posts

Re: OpenAI's plans according to Sam Altman

#51

Whether scaling laws hold or not, is up for debate. What isn't up for debate, is that: 1) Giant serverfarms are expensive 2) People want on premises/on machine solutions 3) LoRA Tuning of small models continues to excel 4) Thus specialized models continue to evolve at a fast pace 5) Open source foundation models on which tuning can be done are accelerating by the week 6) Performance doesn't matter once a model is "go…

> Whether scaling laws hold or not, is up for debate.

The scaling laws have broken: https://arxiv.org/abs/2210.14891

Re: OpenAI's plans according to Sam Altman

#52
post #16

Earlier quoted context omitted.

1) Giant serverfarms are expensive, but Microsoft has money and savings on scale. This can compare favourably to running locally. 2) People use what LLMs software makers give them and don't care at all about on premise. Software makers want something reliable they can deploy at scale, and not end up debugging problems on a client 4GB machine with an iGPU and multitude of OSs. The actually deciding people want to dele…

> 4) but doing product is icky for OSS people for some reason I am not talking about OSS people. I am talking about integrators. And there is already demand for on premise LLM solutions. Integrators don't ask customers to `git clone` some repo, same as they don't ask them to familiarize themselves with some cloud providers API. They ask them to buy/use the already integrated product. > Note that the Stable Diffusion…

>there is already demand for on premise LLM solutions.

There's also demand for on premise office suits and on premise internal company communication and private smartphones. Guess who controls these markets and how often it's on premise? Unfortunately, experience suggests users would drop privacy for convenience...

>Integrators

Here the requirements are far more complex than for the SD case. SD can run standalone, or as plugin. Its users are adapt, tend to have good GPUs, and there isn't that much relevant software - one can do a bespoke solution for each (a PS plugin is enough to keep many happy). For LLMs, either you supply a cloud API, or deal with a significant deployment burden nobody AFAIK has even started handling. Not to mention the licenses...

Current best hope for on-premise is that one of the OS makers decides to do the work and does it well enough we could trust it.

Re: OpenAI's plans according to Sam Altman

#53
post #17
post #14

Earlier quoted context omitted.

> Most people don't care about local and private. Right, but corporations do. And AI is a revolution because it makes workers substantially more efficient, not because it makes for a slightly better Google. If corporations want to leverage AI to make their workforce more efficient, it must be local and private in many cases. OpenAI is already experiencing friction in the EU.

Same corporations happily use Office 365 and GSuite for all their documents rather than a local and private solution. I'm sure they'll come to a similar arrangement with regard to AI.

That doesn't change the fact that these corporations have an interest in data privacy and cost reduction. To wit, if MS wouldn't guarantee data security in european datacenters, they would be way less competitive in the EU.

Many corporations run their own datacenters, have on premises mailservers and run their own backup solutions. Not everything is in the cloud.

Re: OpenAI's plans according to Sam Altman

#54
post #35

Earlier quoted context omitted.

1) Did you do the math? Makes no intuitive sense to me. 2) did you do a survey? Because I see no reason to just assume no one wants or needs on-prem. 3) you're extrapolating the current state of affairs into the future with no logical justification for doing so. 4) This just relies on 1-3 and is also only speculation. I can easily see scenarious where big tech fail to pivot into AI properly and go down.

1) I can't do the complete math since I don't know the exact costs, but basically: A) Running a remote cloud LLM costs about nothing in dollars to the user. B) Running a remote cloud LLM does cost for the provider. Note however Microsoft and Google are the cloud, so they don't have to pay the absurd profit margins. They already have specialized hardware and can bring their costs down. C) Microsoft and Google can prob…

> Running a remote cloud LLM costs about nothing in dollars to the user.

The user doesn't care where it runs, because the user interacts with my product, not my backend. He also doesn't pay my cloud provider, he pays me.

I think we don't need to argue the fact that an on premise solution is cheaper than a cloud solution for a lot of tasks, especially when talking about bounded resources. There is some convenience in setup, and some maintenance tasks are easier, but this comes at significant costs, especially as projects get larger.

> Hopefully being based on more than predictions of local LLM performance.

What else should they be based on, pray, given the fact that smaller models suitable for on-premise and even on-machine use are improving rapidly? https://arxiv.org/pdf/2303.16199.pdf

Are they at the performance levels of cloud based very large LLMs? Not yet. But their turnover times are measured in weeks, not months. And it's not a question if there will be a higher quality base model, only when that will happen.

Re: OpenAI's plans according to Sam Altman

#55
post #52

Earlier quoted context omitted.

> 4) but doing product is icky for OSS people for some reason I am not talking about OSS people. I am talking about integrators. And there is already demand for on premise LLM solutions. Integrators don't ask customers to `git clone` some repo, same as they don't ask them to familiarize themselves with some cloud providers API. They ask them to buy/use the already integrated product. > Note that the Stable Diffusion…

>there is already demand for on premise LLM solutions. There's also demand for on premise office suits and on premise internal company communication and private smartphones. Guess who controls these markets and how often it's on premise? Unfortunately, experience suggests users would drop privacy for convenience... >Integrators Here the requirements are far more complex than for the SD case. SD can run standalone, or…

> Guess who controls these markets

These markets benefit from deep OS integration, interconnectivity between users products and a long history of "we have always used Word". None of that is the case for LLMs.

> For LLMs, either you supply a cloud API, or deal with a significant deployment burden nobody AFAIK has even started handling.

Why would there be a deployment burden? The actual setup isn't hard, the rest is wrapping the thingamabob into an API the product can use...same btw. as I have to do for cloud-LLM APIs, because the product ideally wants to be able to use different providers, so I have to abstract the API away anyway.

Sure, I have to worry about infrastructure, maintenance, and performance characteristics, but that's hardly different from running our databases or web-backends.

> Current best hope for on-premise is that one of the OS makers decides to do the work and does it well enough we could trust it.

Why? I don't have to trust the OS providers to integrate, say, postgres or nginx or redis either. Why would I need their help to run another piece of software that lives entirely in userspace?

Re: OpenAI's plans according to Sam Altman

#56
post #40

Earlier quoted context omitted.

> Another issue is deployment. Imagine this: You are a software developer using an LLM in your commercial product. You have two/three choices. > Call a cloud API using a simple cross-platform HTTP call. This will reliably work. While at it, you may gain useful data on your customers In the not too distant future, I expect most applications to be replaced by LLM assistants. So the above scenario won't really happen. Y…

>>Call a cloud API using a simple cross-platform HTTP call. This will reliably work. While at it, you may gain useful data on your customers. >In the not too distant future, I expect most applications to be replaced by LLM assistants. So the above scenario won't really happen. Regardless we have the question of how to deploy the local LLM. If the frontend will be the OS, than we can be reliably sure that Microsoft an…

> Regardless we have the question of how to deploy the local LLM.

The same as we do any other software? There is nothing inherently more difficult in deploying an ML model than there is, say, in setting up a redudant high traffic RDBMS.

> If the frontend will be the OS

Why would the frontend be the OS? The OS isn't the frontend to my database. The OS isn't my IDE. The OS isn't the games I play. The OS isn't even my browser.

All these are Userspace programs.

Re: OpenAI's plans according to Sam Altman

#57
post #52

Earlier quoted context omitted.

>there is already demand for on premise LLM solutions. There's also demand for on premise office suits and on premise internal company communication and private smartphones. Guess who controls these markets and how often it's on premise? Unfortunately, experience suggests users would drop privacy for convenience... >Integrators Here the requirements are far more complex than for the SD case. SD can run standalone, or…

> Guess who controls these markets These markets benefit from deep OS integration, interconnectivity between users products and a long history of "we have always used Word". None of that is the case for LLMs. > For LLMs, either you supply a cloud API, or deal with a significant deployment burden nobody AFAIK has even started handling. Why would there be a deployment burden? The actual setup isn't hard, the rest is wr…

>These markets benefit from deep OS integration, interconnectivity between users products and a long history of "we have always used Word". None of that is the case for LLMs.

The old moats did not stop existing because LLMs came along. e.g. a big use case for LLMs is running over one's own documents. We can guess who very likely already has access (MS and Google), and who is going to get a scary permission prompt at best (everyone else). OS integration is obviously coming, MS announced Copilot and Google can just silently upgrade Assistant. We may not be far from a repeat of the IE saga, where MS declares Copilot as essential part of Windows.

My point is that commercial demand for privacy is not enough, and may not prevent Cloud APIs from dominating.

>>For LLMs, either you supply a cloud API, or deal with a significant deployment burden >Why would there be a deployment burden? The actual setup isn't hard, the rest is wrapping the thingamabob into an API the product can use...

Well, the entire idea is to run locally, right? Now you have to worry about getting the runtime to work on 3 different OSs, and many many hardware variations (like the many Intel AVX variants, low memory configurations, etc.). Just take a look at the recent moves to flatpack/snap everything, and that's merely due to software variations on a single OS.

>Why? I don't have to trust the OS providers to integrate, say, postgres or nginx or redis either. Why would I need their help to run another piece of software that lives entirely in userspace?

I expect LLMs to be a ubiquitous UI paradigm. We do expect OS providers to bundle a UI kit, and not everyone to roll their own, right?

Besides, you are comparing to server software. But non-cloud LLMs are expected to run locally on clients. That's a different world. Clients are a lot more diverse, weaker in processing power, and most can't handle upgrading postgres.

All that said, perhaps we should look at legislation as well as the possibility of a OS provider playing nice. We're talking about a lot of data/power in the hands of a few corps.

Re: OpenAI's plans according to Sam Altman

#58
post #40

Earlier quoted context omitted.

>>Call a cloud API using a simple cross-platform HTTP call. This will reliably work. While at it, you may gain useful data on your customers. >In the not too distant future, I expect most applications to be replaced by LLM assistants. So the above scenario won't really happen. Regardless we have the question of how to deploy the local LLM. If the frontend will be the OS, than we can be reliably sure that Microsoft an…

> Regardless we have the question of how to deploy the local LLM. The same as we do any other software? There is nothing inherently more difficult in deploying an ML model than there is, say, in setting up a redudant high traffic RDBMS. > If the frontend will be the OS Why would the frontend be the OS? The OS isn't the frontend to my database. The OS isn't my IDE. The OS isn't the games I play. The OS isn't even my b…

>Why would the frontend be the OS?

I answered this above.

https://news.ycombinator.com/item?id=36194304

Re: OpenAI's plans according to Sam Altman

#59
post #35

Earlier quoted context omitted.

1) I can't do the complete math since I don't know the exact costs, but basically: A) Running a remote cloud LLM costs about nothing in dollars to the user. B) Running a remote cloud LLM does cost for the provider. Note however Microsoft and Google are the cloud, so they don't have to pay the absurd profit margins. They already have specialized hardware and can bring their costs down. C) Microsoft and Google can prob…

> Running a remote cloud LLM costs about nothing in dollars to the user. The user doesn't care where it runs, because the user interacts with my product, not my backend. He also doesn't pay my cloud provider, he pays me. I think we don't need to argue the fact that an on premise solution is cheaper than a cloud solution for a lot of tasks, especially when talking about bounded resources. There is some convenience in…

>I think we don't need to argue the fact that an on premise solution is cheaper than a cloud solution for a lot of tasks

In the absolute sense where we look at the total cost of running the model (and not care how it's distributed or include profits), you may be right even with scale efficiencies - making a determination requires data about cloud server costs we do not have. But I can make an informed guess about the dollar cost the user sees.

The cost the user sees is influenced by the factor called 'Microsoft and Google (etc.) have a lot of money, and seem to be perfectly willing to absorb costs to control the market and get user data', and that's enough to get user costs very low when calling to Cloud LLMs.

>>>I can easily see scenarious where big tech fail to pivot into AI properly and go down.

>>I don't think you have much to base scenarios where big tech goes down upon, but I'll be glad to hear an argument. Hopefully being based on more than predictions of local LLM performance.

>What else should they be based on, pray, given the fact that smaller models suitable for on-premise and even on-machine use are improving rapidly?

My consistent point is that technical performance is not enough. While the small open models have a tendency to overclaim[0], they'll get to GPT-4 level in time.

Success, however, is not determined by technical performance alone. There are some very big hurdles ahead. Why should big tech fall when they pivoted ahead in time, and maintain some very useful moats?

[0] https://arxiv.org/abs/2305.15717

Re: OpenAI's plans according to Sam Altman

#60
post #24
post #20

Is there a reason this post is pointing to a capture of the article at archive.org rather than to the original Humanloop webpage?

It was removed: https://humanloop.com/blog/openai-plans "This content has been removed at the request of OpenAI."

https://web.archive.org/web/20230531203946/https://humanloop... https://archive.is/rcbem
Post reply on HN