EfficientZero VS DeepSpeed

Here's an algorithm that is more sample efficient : https://github.com/YeWR/EfficientZero

Use multiprocessing to have more GPU workers could help. My code based on EfficientZero https://github.com/YeWR/EfficientZero is utilizing CPUs and GPUs to 90%. It uses Ray for multiprocessing and splits Reanalyze into CPU and GPU workers to maximize resource utilization. By the way, it's not converging to optimal policy well: it gets stuck at 50% optimal episode return at with a small amount of training. Have you had this issue before?

Found relevant code at https://github.com/YeWR/EfficientZero + all code implementations here

Mastering Atari Games with Limited Data – EfficientZero ( Human sample -efficiency! ) Paper: https://arxiv.org/abs/2111.00210 Lesswrong article about the paper: https://www.lesswrong.com/posts/mRwJce3npmzbKfxws/efficientzero-how-it-works Github: https://github.com/YeWR/EfficientZero

Have you seen https://github.com/YeWR/EfficientZero EfficientZero yet? This agent is able to solve problems with unknown rules, where the agent starts only with information about the shape of the inputs and reward feedback. With superhuman ability - it needs less training data than humans do - and SoTA trumping results on the problems it has been tried on. (various atari/Go/chess/etc)

Open-source codebase for EfficientZero - am I missing something or the repo is empty?

Code: https://github.com/YeWR/EfficientZero

Code for https://arxiv.org/abs/2111.00210 found: https://github.com/YeWR/EfficientZero

DeepSpeed can handle parallelism concerns, and even offload data/model to RAM, or even NVMe (!?) . I'm surprised I don't see this project used more.

While on the surface, a 192GB Mac Studio seems like a great deal (it's not much more than a 48GB A6000!), there are several reasons why this might not be a good idea:

* I assume most people have never used llama.cpp Metal w/ large models. It will drop to CPU speeds whenever the context window is full: https://github.com/ggerganov/llama.cpp/issues/1730#issuecomm... - while sure this might be fixed in the future, it's been an issue since Metal support was added, and is a significant problem if you are actually trying to actually use it for inferencing. With 192GB of memory, you could probably run larger models w/o quantization, but I've never seen anyone post benchmarks of their experiences. Note that at that point, the limited memory bandwidth will be a big factor.

* If you are planning on using Apple Silicon for ML/training, I'd also be wary. There are multi-year long open bugs in PyTorch[1], and most major LLM libs like deepspeed, bitsandbytes, etc don't have Apple Silicon support[2][3].

You can see similar patterns w/ Stable Diffusion support [4][5] - support lagging by months, lots of problems and poor performance with inference, much less fine tuning. You can apply this to basically any ML application you want (srt, tts, video, etc)

Macs are fine to poke around with, but if you actually plan to do more than run a small LLM and say "neat", especially for a business, recommending a Mac for anyone getting started w/ ML workloads is a bad take. (In general, for anyone getting started, unless you're just burning budget, renting cloud GPU is going to be the best cost/perf, although on-prem/local obviously has other advantages.)

[1] https://github.com/pytorch/pytorch/issues?q=is%3Aissue+is%3A...

[2] https://github.com/microsoft/DeepSpeed/issues/1580

[3] https://github.com/TimDettmers/bitsandbytes/issues/485

[4] https://github.com/AUTOMATIC1111/stable-diffusion-webui/disc...

[5] https://forums.macrumors.com/threads/ai-generated-art-stable...

And https://github.com/microsoft/deepspeed

DeepSpeed Chat: Easy, Fast and Affordable RLHF Training of ChatGPT-like Models at All Scales (https://github.com/microsoft/DeepSpeed/tree/master/blogs/deepspeed-chat)