Firefox Desktop 151 Adds `Web Serial API` Support

// related

• #0001

  #0001OtherGeekNews18 hours ago

  `Utilyze` Measures How Efficiently GPUs Do Useful Work

  40radar

  UtilyzeGPU monitoring tool — shows real usage via performance counters

  Standard GPU monitors can report 100% usage even when only a small slice of hardware is doing real work. This is a niche but handy debugging tool for local inference or media workloads.

  • —nvidia-smi and nvtop mainly show whether kernels are running, so utilization can look saturated while real hardware use stays low.
  • —Utilyze reads GPU performance counters directly and shows live resource usage. Bottleneck diagnosis gets more concrete than a single utilization percent.
  • —Best fit is local LLM, image, video, or CUDA experiments where GPU cost and runtime matter. General web app work can ignore it.

  Source: news.hada.io/topic?id=29749Read original →
• #0002

  #0002Otherr/LocalLLaMAyesterday

  `ik_llama.cpp` pushes `Qwen3.6 35B A3B` near 110 tok/s on 12GB VRAM

  40radar

  ik_llama.cppllama.cpp fork — optimized CPU offload and quantization

  MTP plus CPU offload can make a local MoE model feel interactive on consumer hardware. Useful for private coding or batch jobs, but still a setup-specific benchmark.

  • —Same IQ4_XS quant averaged 89.76 tok/s on regular llama.cpp; ik_llama.cpp samples reached roughly 105-110 tok/s.
  • —Hardware was RTX 4070 Super 12GB, Ryzen 7 9700X, and 48GB DDR5. CPU offload quality matters as much as VRAM.
  • —Benchmark used --ctx-size 131072, q8 KV cache, and draft-mtp; long-context local workflows remain memory-sensitive.
  • —Treat it as a tuning lead, not a buying guide. Kernel, quant, and fork versions can swing results hard.

  Source: www.reddit.com/r/LocalLLaMA/comments/1tjh7az/110_toks_wiRead original →
• #0003

  #0003OtherGeekNews2 days ago

  Firefox 148 Starts Turning Off `asm.js` Optimization

  40radar

  Legacy asm.js still runs, but loses its fast path in Firefox. Old web games and compute-heavy demos should move to WebAssembly; new products can ignore this.

  • —From Firefox 148, SpiderMonkey disables asm.js optimization by default, with removal planned later.
  • —Compatibility remains because asm.js is a JavaScript subset; the breakage risk is performance, not execution.
  • —Existing asm.js assets should be migrated to WebAssembly. For new builds, do not target asm.js.

  Source: news.hada.io/topic?id=29732Read original →