762 karma · joined May 18, 2020
A search for model pruning turns out many results, including https://arxiv.org/abs/2305.11627 which discusses "magnitude pruning" as a baseline, and refers to https://arxiv.org/pdf/2301.00774.pdf, which asserts in the introduction:
> First, as shown in Figure 1, SparseGPT can induce uniform layerwise sparsity of up to 60% in e.g. the 175-billion-parameter variant of the OPT family (Zhang et al., 2022), with minor accuracy loss. By contrast, the only known one-shot baseline which easily extends to this scale, Magnitude Pruning (Hagiwara, 1994; Han et al., 2015), preserves accuracy only until 10% sparsity, and completely collapses beyond 30% sparsity.
I don't like how these papers boast their own methods by poorly implementing a baseline and describing their own methods using lots of mathematical jargon - the OP's blog post is a breeze in making the methods accessible to people with very little background.
There are never ending debates on what happened while observing A, but I dislike calling it “quantum teleportation” as it only further confuses people as if any information was teleported during observation. My theory is that A and B are totally independent until both observations reach a middleman C, and it’s at this point that the entanglement starts to matter.
This way, even if the paper itself is hard to read, for the good ones I do expect someone else to leave a comment with a sketch of the most interesting parts of the paper that would get upvoted to the top, and the author could click a "promote" button or something to make it official. This way the author doesn't have to write very well as long as the paper is valuable enough for someone else to be interested.
What I do prefer is something like a GUI with features like previewing detections and specifying data for training, maybe in the form of built-in components, which would have a smoother learning curve but still allow me to dig deeper whenever needed. Any such tools available?
> Our empirical investigations show the effectiveness of our methods, which allow us to estimate the embedding size of OpenAI’s gpt-3.5-turbo to be about 4,096.
Discussion of the other paper is at https://news.ycombinator.com/item?id=39675735 but DeepMind seems to care more about helping their peer keep secrets and did not release GPT-3.5’s embedding size. Also the other paper is mentioned in Section 9 “Simultaneous discovery” of this paper in case anyone wonders.
If I understand correctly, they simply asked the participants themselves if they are BS’ing and drew the conclusions solely from that? How do you expect people BS’ing others would admit doing that?
If you know a little about the math behind gradient descent you can see that an embedding layer followed by a softmax layer gives you exactly the best Bayes estimate. If you want a bit of structure, like every word depends on previous n words, you get a convolutional RNN which is also well studied. These ideas are natural and elegant but maybe a better idea is to comprehend the research already done to avoid diving into dead ends too much.
I don't think it's a good idea to introduce over 20 different methods before talking about the correct one that works for any number of dimensions, say n, and the reason behind its correctness is very obvious:
* Generate a random vector by sampling n standard normal distributions: `vector = np.random.randn(n)`
* Key step: show that the vector has a uniform direction.
The proof is as follows: you look at the probability density function of a normal distribution, which is `p(x)=1/sqrt(2pi)*exp(-x^2/2)`, and the probability density function of the vector is the product of all these densities of its individual dimensions. Now the product `p(x1)p(x2)...p(xn)=1/sqrt(2pi)^n*exp(-(x1^2+x2^2+...+xn^2)/2)` since `exp(a)exp(b)=exp(a+b)` due to power functions.
Now it's easy to see that probability density is invariant to vector length, which means the vector has uniform probability for any specific value of x1^2+x2^2+...+xn^2. Whatever rotation you apply after sampling this vector, since rotation preserves x1^2+x2^2+...+xn^2 by definition, you get the exact same probability density function and therefore the same distribution of vectors.
* Now that the direction of the vector is uniformly sampled, decide the radius separately: for n-sphere the radius is just 1, and for n-ball the volume of the radius is proportional to the nth power of the radius, so you sample a uniform number from [0,1] as the volume and take the nth root as the radius: `radius = np.random.uniform(0, 1)*(1/n)`
* Normalize the vector to the radius: `vector = vector / np.sqrt((vector*2).sum()) * radius`
I think Section 2 of this book provides a much better perspective on the problem of generating uniform random points, since it also provides intuition behind the geometry of high dimensions and properties of the unit ball, etc.
1. Emulating a desktop with windows so smoothly on both desktop and mobile. This webapp is much snappier than most webapps these days.
2. A storage and file explorer with a friendly API for third party apps. Now any app can use a cloud storage synced across devices where the storage costs are paid by the user.
Can't wait until more apps are available! I see some limitations like VS Code unable to open git repositories which seems a limitation of the storage API (append-only, cannot seek or download partially)? Hope it gets closer to native experience in the future
I think the problem with the article is that it emphasized the absolute acquisition value and omitted the fact that the company raised $400M. Considering the amount they raised, $559M seems much more reasonable and not quite bad terms?
1. Offer “free static website” with lots of templates and guides to help you build one
2. The first 100GB is free and beyond that it’s $0.01/MB. But no worries! Very few customers actually use up that free bandwidth and in case you need more you can purchase packages for $100/TB. Also we offer a free service that will help you get your site more visible by advertising it, it’s included by default.
3. After a month or so, randomly help a customer bump the website and make it popular by putting it in some list that is frequently crawled. Secretly hire someone else to crawl these websites and make lots of download requests
4. Once the customer suddenly gets 10TB of traffic, bill them for 9900GB which is $99000
5. As long as 1 out of 100 customers pay, you are profiting $990 per customer! For the rest of customers, offer a 5% discount so they only have to pay $1980. Threat taking them to collections if they refuse.
Become the next millionare by just selling free static websites to 1000 customers! Anyone join us?
I think this is awesome but maybe it’s not really that surprising given how this “generate and then finetune” approach has already worked so well?
> ... > In conclusion, while the passage does provide a basic account of the incident, its lack of detail, reliance on jargon, and vague explanations leave room for skepticism regarding the severity of the issue, the transparency of the response, and the effectiveness of preventative measures. A more thorough and less technical explanation could have mitigated some of these concerns.
Cloudflare's postmortem: (https://blog.cloudflare.com/cloudflare-outage-on-june-21-202...)
> In summary, the passage does not exhibit overt deception, manipulation, or dishonesty. Cloudflare's statement seems to be a forthright attempt to explain what happened, accept responsibility, and outline steps to prevent future incidents. The inclusion of technical details and the acknowledgment of their error reflect a commitment to transparency, even if the promotional content at the end might seem slightly incongruent with the preceding apology and explanation.
Now the thing is to make a fast and reliable plugin that automatically puts the warning on the webpage and shame these corporates
Do you think OpenAI’s superalignment will ever allow you to make such a model?