正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

gpu kernels on on my computer writing other gpu kernels for the same chip to simulate 100ks of particles, each an agent + neural network sensing K bg fields and allocating energy to A actions, at 1000s steps/s, for thermodynamic artificial life i think maybe not a bubble lads

Fraser Price

1,191 subscribers

32,653 次观看 • 2 个月前 •via X (Twitter)

健康养生教育科学技术

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Today I release new GPU Particle Volumes system and the GPU Snow Particle shaders for it! This snow shader can render hundreds of thousands of particles at the same time even on a weak GPU. It also supports VRC Light Volumes. Get it on my Booth or Patreon!

Today I release new GPU Particle Volumes system and the GPU Snow Particle shaders for it! This snow shader can render hundreds of thousands of particles at the same time even on a weak GPU. It also supports VRC Light Volumes. Get it on my Booth or Patreon!

RED_SIM

43,816 次观看 • 9 个月前

It's here: We just hit superhuman performance on AI kernel optimization! Real customer models & production settings. Not toy problems (what I typically see). This is the year that Claude writes its own kernels, Codex its own kernels, for every new GPU that it wants to run on -- something that takes months to port between GPU generations today. This has a massive impact to scaling intelligence. More compute means getting the next frontier model sooner.

It's here: We just hit superhuman performance on AI kernel optimization! Real customer models & production settings. Not toy problems (what I typically see). This is the year that Claude writes its own kernels, Codex its own kernels, for every new GPU that it wants to run on -- something that takes months to port between GPU generations today. This has a massive impact to scaling intelligence. More compute means getting the next frontier model sooner.

Sharon Zhou

241,935 次观看 • 6 个月前

timelapse #164 (15.5 hrs) - Burning midnight oil with the Kimi team benchmarking on kernels - Getting a Persistent Fused Mega Kernel for a Puffer Lib Environment (the full Craftax game) - Dipped for the night to have models run my overnight training runs on autopilot, including some kernel-based GRPO on qwen3.6 - private contract work - downloaded 1.1 TB of minecraft videos to train a foundation model on - optimized my minecraft foundation model training pipeline and kernels to train on 500k hrs of 128px at 10 fps in ~28 hrs on single gpu (5 hrs of learning per second on rtx pro 6000 blackwell) - doing it for the love of the game

timelapse #164 (15.5 hrs) - Burning midnight oil with the Kimi team benchmarking on kernels - Getting a Persistent Fused Mega Kernel for a Puffer Lib Environment (the full Craftax game) - Dipped for the night to have models run my overnight training runs on autopilot, including some kernel-based GRPO on qwen3.6 - private contract work - downloaded 1.1 TB of minecraft videos to train a foundation model on - optimized my minecraft foundation model training pipeline and kernels to train on 500k hrs of 128px at 10 fps in ~28 hrs on single gpu (5 hrs of learning per second on rtx pro 6000 blackwell) - doing it for the love of the game

Elliot Arledge

28,210 次观看 • 1 个月前

Ex-NVIDIA engineer who built Unsloth explained RL, kernels, reasoning, quantization, and agents in 2 hours 42 minutes - better than $5000 fine-tuning bootcamps. pick the base model -> write triton kernels for 2x faster fine-tune -> quantize to 4-bit -> run GRPO/DPO -> ship a reasoning model on your single GPU. That loop is why Unsloth is the default way to fine-tune Llama, Qwen, Gemma, and Phi on hardware you already own. Unsloth + Triton kernels + 4-bit quantization + GRPO/DPO + single-GPU fine-tuning - that's the stack. Watch and save it, then fine-tune your first model tonight.

Ex-NVIDIA engineer who built Unsloth explained RL, kernels, reasoning, quantization, and agents in 2 hours 42 minutes - better than $5000 fine-tuning bootcamps. pick the base model -> write triton kernels for 2x faster fine-tune -> quantize to 4-bit -> run GRPO/DPO -> ship a reasoning model on your single GPU. That loop is why Unsloth is the default way to fine-tune Llama, Qwen, Gemma, and Phi on hardware you already own. Unsloth + Triton kernels + 4-bit quantization + GRPO/DPO + single-GPU fine-tuning - that's the stack. Watch and save it, then fine-tune your first model tonight.

h100envy

496,112 次观看 • 2 个月前

I implemented Google Research's TurboQuant as a CUDA-native compression engine on Blackwell B200. 5x KV cache compression on Qwen 2.5-1.5B, near-loseless attention scores, generating live from compressed memory. 5 custom cuTile CUDA kernels ft: - fused attention (with QJL corrections) - online softmax -on-chip cache decompression - pipelined TMA loads Try it out: s/o Bryce, the CUDA Colonel and the cuTile team at NVIDIA for lending me Blackwell GPU access :) cc sunny madra Gavin

I implemented Google Research's TurboQuant as a CUDA-native compression engine on Blackwell B200. 5x KV cache compression on Qwen 2.5-1.5B, near-loseless attention scores, generating live from compressed memory. 5 custom cuTile CUDA kernels ft: - fused attention (with QJL corrections) - online softmax -on-chip cache decompression - pipelined TMA loads Try it out: s/o Bryce, the CUDA Colonel and the cuTile team at NVIDIA for lending me Blackwell GPU access :) cc sunny madra Gavin

ani

813,740 次观看 • 5 个月前

every other day i yearn for more research fields to adopt the culture from the ML and ML adjacent fields of building a demo website for each paper and put code on github

every other day i yearn for more research fields to adopt the culture from the ML and ML adjacent fields of building a demo website for each paper and put code on github

outside five sigma

27,352 次观看 • 11 个月前

$Announcing the limited alpha release of our GPU marketplace, with $50 in free credits for 100 selected testers—apply now for a chance to participate! 🤘🏼🌪️ Hyperbolic’s GPU marketplace optimizes global GPU infrastructure, aggregating resources from data centers, mining farms, personal machines, and on-prem setups to make GPUs accessible at a fraction of the cost. Apply to gain access:$

Announcing the limited alpha release of our GPU marketplace, with $50 in free credits for 100 selected testers—apply now for a chance to participate! 🤘🏼🌪️ Hyperbolic’s GPU marketplace optimizes global GPU infrastructure, aggregating resources from data centers, mining farms, personal machines, and on-prem setups to make GPUs accessible at a fraction of the cost. Apply to gain access:

Hyperbolic

26,204 次观看 • 2 年前

THE MS-A2 IS THE MINISFORUM BOX HERMES AGENT WAS NEVER MEANT TO RUN ON, AND THAT'S BY DESIGN The MS-S1 MAX earns its spot running Hermes Agent because of one thing. 128GB of unified memory, up to 96GB of it handed straight to the GPU. That's the only reason a 120B model fits and runs locally for $0 a month The MS-A2 solves a different problem. Ryzen 9 9955HX, 16 cores, 32 threads, up to 96GB of regular DDR5-5600, no unified pool Three M.2 PCIe 4.0 slots, one U.2, two 22110. Dual 10Gbps SFP+ LAN plus 2.5G. WiFi 6E. Bluetooth 5.3. A slide-out motherboard for fast upgrades. A real PCIe x16 slot that actually takes a low-profile GPU That last part is where the two machines split for good. The MS-S1 MAX's PCIe slot won't take a GPU at all, every bit of GPU power has to come from the unified chip itself. The MS-A2 trades that unified memory trick for raw expandability instead One box runs a local AI agent. The other runs a home lab that needs storage, networking, and room to grow. Minisforum built both on purpose, not as the same product wearing two names

NO1ennn

25,645 次观看 • 2 个月前

Without the Pauli Exclusion Principle, every electron in every atom would collapse to the lowest energy level. No chemistry. No molecules. No life. No hardware to run Claude on. It's not a fundamental law — it's a consequence of wavefunctions being anti-symmetric. Two identical fermions in the same quantum state cancel each other out completely. Every GPU chip, every transistor, every bit of silicon that runs GPT exists because of this one sign flip. 19 minutes. Bookmark & watch today. The universe runs on antisymmetry.

Without the Pauli Exclusion Principle, every electron in every atom would collapse to the lowest energy level. No chemistry. No molecules. No life. No hardware to run Claude on. It's not a fundamental law — it's a consequence of wavefunctions being anti-symmetric. Two identical fermions in the same quantum state cancel each other out completely. Every GPU chip, every transistor, every bit of silicon that runs GPT exists because of this one sign flip. 19 minutes. Bookmark & watch today. The universe runs on antisymmetry.

Eron

21,199 次观看 • 28 天前

UC Berkeley just open-sourced FreeToken. (2–4x faster local LLM inference than Ollama) the results are wild: - Qwen3.6-35B on an 8GB GPU at 39.3 tokens/s - DeepSeek-V4-Flash 284B on a 32GB GPU at 22 tokens/s - GLM-5.2 753B on a 96GB GPU at 14.9 tokens/s a 35B model at 16-bit precision needs about 70GB just for its weights. even at 4 bits it is close to 18GB, and FreeToken serves it on an 8GB GPU. let me explain how: all three models mentioned above are Mixture-of-Experts, and that is what FreeToken takes advantage of. each layer holds hundreds of separate experts plus a small router that picks a few of them per token. Qwen3.6-35B activates roughly 3B of its 35B parameters per token. DeepSeek-V4-Flash picks 6 of 256 experts per layer, so 13B of its 284B run at a time. so compute was never the bottleneck. the weights a single step touches fit comfortably on a consumer GPU. every expert the router might pick still has to exist somewhere. they sit in system RAM, and the GPU keeps a cache of the ones the model has been using recently. so everything comes down to what happens when the router picks an expert that is not on the GPU. there are two ways to serve that miss: 1. copy it over PCIe and run it on the GPU 2. run it on the CPU, where it already lives both read from the same system memory, so they compete for one pool of bandwidth instead of adding to each other. existing engines pick one option and freeze it when the model loads. but routing changes on every token, so a fixed choice misses most of what the model asks for. FreeToken measures both bandwidths on your machine and splits each step's misses between the two paths in proportion. the GPU and CPU results then merge exactly, with no approximation. two machines with the same GPU can end up wanting opposite strategies, which I did not expect. a 5090 in a gaming desktop should push nearly everything over PCIe, while an 8GB laptop is better off computing most misses on the CPU. none of that is readable off a spec sheet, so the engine profiles it once per machine. the second half of the design is about agents. coding agents constantly rewrite their own history, and every edit normally forces thousands of tokens back through prefill. FreeToken saves its checkpoints at the exact boundaries agent frameworks cut on, so it only reprocesses the new part. its slowest first token stays under 44 seconds, while llama.cpp peaks at 232 and KTransformers at 946. it serves the OpenAI and Anthropic APIs under Apache 2.0, so Claude Code and Codex can point at it directly. releasing weights publicly decides who can download a model, not who can afford to run one. frontier open models keep shipping, and running them still assumes a rented cluster. meanwhile there are over a hundred million consumer machines with discrete GPUs sitting mostly idle. closing that gap was never a hardware problem, and work like this is what turns open weights into something you can actually use. paper: repo: almost every idea in this post, from why memory bandwidth decides the outcome to why moving weights costs more than computing on them, comes straight out of how a GPU is built. I wrote a detailed primer on that. the article is quoted below.

UC Berkeley just open-sourced FreeToken. (2–4x faster local LLM inference than Ollama) the results are wild: - Qwen3.6-35B on an 8GB GPU at 39.3 tokens/s - DeepSeek-V4-Flash 284B on a 32GB GPU at 22 tokens/s - GLM-5.2 753B on a 96GB GPU at 14.9 tokens/s a 35B model at 16-bit precision needs about 70GB just for its weights. even at 4 bits it is close to 18GB, and FreeToken serves it on an 8GB GPU. let me explain how: all three models mentioned above are Mixture-of-Experts, and that is what FreeToken takes advantage of. each layer holds hundreds of separate experts plus a small router that picks a few of them per token. Qwen3.6-35B activates roughly 3B of its 35B parameters per token. DeepSeek-V4-Flash picks 6 of 256 experts per layer, so 13B of its 284B run at a time. so compute was never the bottleneck. the weights a single step touches fit comfortably on a consumer GPU. every expert the router might pick still has to exist somewhere. they sit in system RAM, and the GPU keeps a cache of the ones the model has been using recently. so everything comes down to what happens when the router picks an expert that is not on the GPU. there are two ways to serve that miss: 1. copy it over PCIe and run it on the GPU 2. run it on the CPU, where it already lives both read from the same system memory, so they compete for one pool of bandwidth instead of adding to each other. existing engines pick one option and freeze it when the model loads. but routing changes on every token, so a fixed choice misses most of what the model asks for. FreeToken measures both bandwidths on your machine and splits each step's misses between the two paths in proportion. the GPU and CPU results then merge exactly, with no approximation. two machines with the same GPU can end up wanting opposite strategies, which I did not expect. a 5090 in a gaming desktop should push nearly everything over PCIe, while an 8GB laptop is better off computing most misses on the CPU. none of that is readable off a spec sheet, so the engine profiles it once per machine. the second half of the design is about agents. coding agents constantly rewrite their own history, and every edit normally forces thousands of tokens back through prefill. FreeToken saves its checkpoints at the exact boundaries agent frameworks cut on, so it only reprocesses the new part. its slowest first token stays under 44 seconds, while llama.cpp peaks at 232 and KTransformers at 946. it serves the OpenAI and Anthropic APIs under Apache 2.0, so Claude Code and Codex can point at it directly. releasing weights publicly decides who can download a model, not who can afford to run one. frontier open models keep shipping, and running them still assumes a rented cluster. meanwhile there are over a hundred million consumer machines with discrete GPUs sitting mostly idle. closing that gap was never a hardware problem, and work like this is what turns open weights into something you can actually use. paper: repo: almost every idea in this post, from why memory bandwidth decides the outcome to why moving weights costs more than computing on them, comes straight out of how a GPU is built. I wrote a detailed primer on that. the article is quoted below.

Akshay 🚀

340,691 次观看 • 21 天前

PowerInfer - a high-speed inference engine for deploying LLMs locally. Just came across this super interesting project on speeding up inference. It's not MoE but it's a simple approach that exploits the high locality in LLM inference to design a GPU-CPU hybrid inference engine. Hot-activated neurons are preloaded onto the GPU for fast access, while cold-activated neurons (the majority) are computed on the CPU. This approach significantly reduces GPU memory demands and CPU-GPU data transfer. It achieves an average token generation rate of 13.20 tokens/s, with a peak of 29.08 tokens/s, across various LLMs on a single NVIDIA RTX 4090 GPU. It's on only 18% lower than that achieved by a top-tier server-grade A100 GPU. It also significantly outperforms llama.cpp by up to 11.69x while retaining model accuracy. There is a lot more innovation around inference that's coming fast. Really encouraged by the study on sparse computation to enhance the computational efficiency of LLMs. It's now possible to use PowerInfer with Llama 2 and Faclon 40B. Mistral-7B support is coming soon!

PowerInfer - a high-speed inference engine for deploying LLMs locally. Just came across this super interesting project on speeding up inference. It's not MoE but it's a simple approach that exploits the high locality in LLM inference to design a GPU-CPU hybrid inference engine. Hot-activated neurons are preloaded onto the GPU for fast access, while cold-activated neurons (the majority) are computed on the CPU. This approach significantly reduces GPU memory demands and CPU-GPU data transfer. It achieves an average token generation rate of 13.20 tokens/s, with a peak of 29.08 tokens/s, across various LLMs on a single NVIDIA RTX 4090 GPU. It's on only 18% lower than that achieved by a top-tier server-grade A100 GPU. It also significantly outperforms llama.cpp by up to 11.69x while retaining model accuracy. There is a lot more innovation around inference that's coming fast. Really encouraged by the study on sparse computation to enhance the computational efficiency of LLMs. It's now possible to use PowerInfer with Llama 2 and Faclon 40B. Mistral-7B support is coming soon!

elvis

261,622 次观看 • 2 年前

AMD's Anush Elangovan explains why he thinks his company's open source ethos combined with agentic AI superpowers their leverage as a company: Because AMD publishes a lot of technical details about its hardware, when engineers use AI tools, the models already “understand” AMD’s systems and can help write code for them, debug them, or even generate new tools. And that makes developers more productive on AMD hardware without AMD having to do all the work internally. "AMD has had this ethos of open source, which really plays to our advantage. Every frontier model that I use has already seen every bit of AMD source code." "It'll rewrite my spec for me because it's already in the training data. Which you can't get from closed ecosystems." "In fact I built a virtual GPU simulator just based off our public specs, and now I'm running it on the GPU. So now I can run cross-generational GPU simulations on existing hardware." "We have that advantage. And we've run a Dev Day contest where we generated more tokens on AMD — Triton kernels and HIP kernels — than existed on the internet at the time." "So now that's all part of the pre-training data. It's a superpower because now you're open source, and you're agentically accelerating this process."

AMD's Anush Elangovan explains why he thinks his company's open source ethos combined with agentic AI superpowers their leverage as a company: Because AMD publishes a lot of technical details about its hardware, when engineers use AI tools, the models already “understand” AMD’s systems and can help write code for them, debug them, or even generate new tools. And that makes developers more productive on AMD hardware without AMD having to do all the work internally. "AMD has had this ethos of open source, which really plays to our advantage. Every frontier model that I use has already seen every bit of AMD source code." "It'll rewrite my spec for me because it's already in the training data. Which you can't get from closed ecosystems." "In fact I built a virtual GPU simulator just based off our public specs, and now I'm running it on the GPU. So now I can run cross-generational GPU simulations on existing hardware." "We have that advantage. And we've run a Dev Day contest where we generated more tokens on AMD — Triton kernels and HIP kernels — than existed on the internet at the time." "So now that's all part of the pre-training data. It's a superpower because now you're open source, and you're agentically accelerating this process."

TBPN

34,469 次观看 • 4 个月前

We are excited to share a deeper look into the GPU Sharing Platform that will power AI applications on the InfraX V4 DApp. In this demo we showcase a GPU running and completing an image generation task. Our backend successfully leverages this GPU (and CPU) in real time to complete the job, earning the user money, and powering the infraX platform. Here’s how it works 👉 when you connect to the InfraX DApp, our platform automatically detects the GPU on your machine and immediately checks it eligibility and where it can be used. From there, each user dictates exactly how and when they want to contribute their GPU power by setting the days their PC is most available (throughout the night, for example). Additional, each user will be able to pause their GPU's connection to infraX whenever they need to use it locally, resuming with a just a single click. Once activated, your GPU seamlessly plugs into the InfraX network and begins fulfilling compute jobs, earning YOU money. Go on, take the $INFRA pill..

We are excited to share a deeper look into the GPU Sharing Platform that will power AI applications on the InfraX V4 DApp. In this demo we showcase a GPU running and completing an image generation task. Our backend successfully leverages this GPU (and CPU) in real time to complete the job, earning the user money, and powering the infraX platform. Here’s how it works 👉 when you connect to the InfraX DApp, our platform automatically detects the GPU on your machine and immediately checks it eligibility and where it can be used. From there, each user dictates exactly how and when they want to contribute their GPU power by setting the days their PC is most available (throughout the night, for example). Additional, each user will be able to pause their GPU's connection to infraX whenever they need to use it locally, resuming with a just a single click. Once activated, your GPU seamlessly plugs into the InfraX network and begins fulfilling compute jobs, earning YOU money. Go on, take the $INFRA pill..

infraX | $INFRA

30,615 次观看 • 1 年前

Stress testing Metropolis 1998! - Population: 53,500 - CPU FPS: 80 - GPU FPS: 10-80 - RAM: 3,100 MB So: At the moment, the game is GPU bound. I know why and there's a lot of room for improvement. It will involve developing or customizing an existing GPU framework. There's also a lot of room to improve CPU/RAM, but right now it's in an okay place. #gamedev

Stress testing Metropolis 1998! - Population: 53,500 - CPU FPS: 80 - GPU FPS: 10-80 - RAM: 3,100 MB So: At the moment, the game is GPU bound. I know why and there's a lot of room for improvement. It will involve developing or customizing an existing GPU framework. There's also a lot of room to improve CPU/RAM, but right now it's in an okay place. #gamedev

Yesbox - Metropolis 1998

84,873 次观看 • 1 年前

i spent 3 hours finding the sweet spot for hermes 4.3 36B on a single RTX 3090. saving you the trouble, anon. the model is 21.8GB at Q4_K_M. that leaves 2.2GB free on 24GB VRAM. not much room for KV cache. here's what actually happened: 4K: 35.3 tok/s 8K: 35.2 tok/s 16K: 34.8 tok/s 32K: 34.6 tok/s 64K: 6.4 tok/s 128K: 1.9 tok/s flat from 4K to 32K. then it falls off a cliff at 64K. the trick is quantized KV cache. without it you OOM at 16K. with quantized KV cache you get 32K at full speed. all 64 layers on GPU. at 64K something weird happens. ngl 99 (all layers on GPU) = 3.96 tok/s. the KV cache silently spills to CPU. drop to ngl 55 and speed jumps to 6.37. drop to ngl 48 and it gets worse again (3.46). there's an offload sweet spot where you free just enough VRAM for the cache without losing too much compute to PCIe transfers. 128K works at ngl 32 but you're at 1.95 tok/s. half the model on CPU. usable for batch work, not for interactive. the sweet spot command: llama-server -m hermes-4.3-36b-Q4_K_M.gguf -ngl 99 -c 32768 --cache-type-k q4_0 --cache-type-v q4_0 32K context. 34.6 tok/s. all on GPU. this is where dense 36B lives on 24GB. for comparison, qwen 3.5 (35B MoE, 3B active) holds 112 tok/s from 4K all the way to 262K on the same GPU. no speed drop. same total params, completely different architecture. hybrid linear attention means flat context scaling. dense pays for every token in the KV cache. code and quality comparison coming next. fast vs slow generation side by side in the videos below.

i spent 3 hours finding the sweet spot for hermes 4.3 36B on a single RTX 3090. saving you the trouble, anon. the model is 21.8GB at Q4_K_M. that leaves 2.2GB free on 24GB VRAM. not much room for KV cache. here's what actually happened: 4K: 35.3 tok/s 8K: 35.2 tok/s 16K: 34.8 tok/s 32K: 34.6 tok/s 64K: 6.4 tok/s 128K: 1.9 tok/s flat from 4K to 32K. then it falls off a cliff at 64K. the trick is quantized KV cache. without it you OOM at 16K. with quantized KV cache you get 32K at full speed. all 64 layers on GPU. at 64K something weird happens. ngl 99 (all layers on GPU) = 3.96 tok/s. the KV cache silently spills to CPU. drop to ngl 55 and speed jumps to 6.37. drop to ngl 48 and it gets worse again (3.46). there's an offload sweet spot where you free just enough VRAM for the cache without losing too much compute to PCIe transfers. 128K works at ngl 32 but you're at 1.95 tok/s. half the model on CPU. usable for batch work, not for interactive. the sweet spot command: llama-server -m hermes-4.3-36b-Q4_K_M.gguf -ngl 99 -c 32768 --cache-type-k q4_0 --cache-type-v q4_0 32K context. 34.6 tok/s. all on GPU. this is where dense 36B lives on 24GB. for comparison, qwen 3.5 (35B MoE, 3B active) holds 112 tok/s from 4K all the way to 262K on the same GPU. no speed drop. same total params, completely different architecture. hybrid linear attention means flat context scaling. dense pays for every token in the KV cache. code and quality comparison coming next. fast vs slow generation side by side in the videos below.

Sudo su

52,268 次观看 • 6 个月前

I won an RTX 5090 GPU at Mistral AI worldwide hackathon in Paris, and I have absolutely no idea on how to use it. Here's what I actually built: an image generation model fine-tuned to do technical analysis on trading charts. I trained it on an NVIDIA cloud GPU then back-tested it against Binance historical data. The model was profitable. The jury didn't quite catch the vibe. But apparently someone did because two weeks later, they reached out to tell me I'd won the NVIDIA track. Today, a €4,000 RTX Founders Edition showed up at my door. Absolutely gorgeous piece of hardware. One small problem: I use a MacBook. So if anyone has creative suggestions for what to do with a top-tier GPU and no desktop to put it in… I'm listening Huge thanks to NVIDIA, Mistral AI and Iterate team for appreciating my weird idea and an attempt to push tech to its boundaries

I won an RTX 5090 GPU at Mistral AI worldwide hackathon in Paris, and I have absolutely no idea on how to use it. Here's what I actually built: an image generation model fine-tuned to do technical analysis on trading charts. I trained it on an NVIDIA cloud GPU then back-tested it against Binance historical data. The model was profitable. The jury didn't quite catch the vibe. But apparently someone did because two weeks later, they reached out to tell me I'd won the NVIDIA track. Today, a €4,000 RTX Founders Edition showed up at my door. Absolutely gorgeous piece of hardware. One small problem: I use a MacBook. So if anyone has creative suggestions for what to do with a top-tier GPU and no desktop to put it in… I'm listening Huge thanks to NVIDIA, Mistral AI and Iterate team for appreciating my weird idea and an attempt to push tech to its boundaries

Kirill

52,518 次观看 • 5 个月前

The Way Forward & A New Chapter For AI powered by GamerHash AI & $GHX. Welcome to the future of bleeding edge connectivity and cloud infrastructure ⚡ GamerHash AI is the answer to the billion dollar question on how to offset the GPU scarcity, enable exponential growth of AI through utilizing consumer-level GPUs and establishing a powerful sharing economy by sourcing a global network of gamers. The synergy of our GPU #DePIN and blockchain for #AI #inference is the technology of the future that already works today. See you in the network!

The Way Forward & A New Chapter For AI powered by GamerHash AI & $GHX. Welcome to the future of bleeding edge connectivity and cloud infrastructure ⚡ GamerHash AI is the answer to the billion dollar question on how to offset the GPU scarcity, enable exponential growth of AI through utilizing consumer-level GPUs and establishing a powerful sharing economy by sourcing a global network of gamers. The synergy of our GPU #DePIN and blockchain for #AI #inference is the technology of the future that already works today. See you in the network!

GamerHash AI

1,866,164 次观看 • 1 年前