Not plain-text I hope. Was this extracted directly from providers? Given the fact that people reuse passwords, it should be easy to construct a larger db theoretically. But this number is mind-boggling.
Might have to look at specific lib implementations, but I'd guess that mostly gpu calls from python are actually happening in c++ land. And internally a lib might be using synchronize calls where needed.
When you call a cuda method, it is launched asynchronously. That is the function queues it up for execution on gpu and returns.
So if you need to wait for an op to finish, you need to `synchronize` as shown above.
`get_current_stream` because the queue mentioned above is actually called stream in cuda.
If you want to run many independent ops concurrently, you can use several streams.
Benchmarking is one use case for synchronize. Another would be if you let's say run two independent ops in different streams and need to combine their results.
Btw, if you work with pytorch, when ops are run on gpu, they are launched in background. If you want to bench torch models on gpu, they also provide a sync api.
I'd imagine that Meta is trying to avoid an AI / LLM monopoly from happening as the primary goal.
They suffered when Apple was a gateway to their service for ios users and decided to shut their access to user data off.
And AI is clearly going to be used widely to aid in content generation if not doing entirely. Also they tried jumping on the chatbot hype with M or something. That didn't pan out as well.
By opening up AI, they would enable tools that allow users to pump out more content easily and spend more time in app.
Getting the goodwill of dev community is a bonus.
A brilliant move from Meta.
Hang in there! And to add to what others have said, I found it extremely helpful to stay away from sad music, romantic shows, etc. until you feel strong again. And keep your body moving!
Glad to see Revolution OS in the list! Helped me get through times in grad school when I'd get stuck on something working on my thesis. Grab a bowl of ramen and put this movie on!
It checks for specific return code. It is useful for testing specific type of failure . Since in shell all non zero return codes are considered failure, we need a way to know that it failed because of the expected reason and not some other bug. So if testing for failure with err code 2, the function will "pass" the test only if the process actually fails with err code 2.
Actually if someone had a model like that, they have all the incentives to keep it a secret. Also it would allow simulations to be ran and make "good" decisions. But we have better odds of cracking the prediction problem than it's responsible use.