Urgent.News

What's breaking now, across thousands of outlets.

Tech

China weighs Nvidia chip purchases by ByteDance, Alibaba

The RTX PRO 5500 is a workstation GPU rather than a data-center AI accelerator.

China weighs Nvidia chip purchases by ByteDance, Alibaba

Nvidia's RTX Spark and Apple's M6 are two powerful processors competing in the markets for small form factor PCs and laptops, as well as high-end Macs. The Nvidia RTX Spark is a new ARM-based SoC that has just recently been announced, while Apple's M6 has been integrated into the refreshed Mac mini running on the latest M6 chip. Both chips boast impressive specifications, but which one comes out on top when it comes to creating, gaming, and AI tasks?

Starting at $899, the Apple M6 is only available in the new Mac mini and comes with varying levels of memory and storage options. The Nvidia RTX Spark, on the other hand, will be available through third-party manufacturers, with prices ranging from around $2,000 for entry-level laptops to custom-built configurations. The Nvidia RTX Spark offers significantly more CPU cores, memory bandwidth, and GPU cores compared to the Apple M6, making it the clear winner in terms of raw computing power.

In terms of performance, the RTX Spark excels in GPU performance, particularly when compared to the Apple M6. While the M6 has a higher single-core performance, the Nvidia chip's multi-core performance provides a substantial advantage, especially when it comes to tasks that require parallel processing such as AI and rendering. Additionally, the Nvidia RTX Spark's RTX Blackwell GPU should deliver exceptional gaming experiences.

Written by urgent.news from TechRadar's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at techinasia.com →

More in Tech

Hello World: Navigating the Complexities of Enterprise Software

Hello, DEV Community! 👋 After spending 2026 building and scaling applications in enterprise environments, I decided it was time to step out of the IDE and share some of the lessons I’ve learned along…

  • Prioritize maintainability over complexity in large-scale systems
  • Emphasize effective communication as the cornerstone of success
  • Respect legacy architecture while planning future migrations

The Code Didn't Change. The Credit Did.

This is a submission for the Kaggle Benchmarking Challenge TL;DR rai-attribution-bench gives nine models a coding session and the attribution rules, then asks who wrote the code.

  • Challenge tested models' authorship identification ability
  • Only incentive structure changed among all variables
  • Synthetic coding sessions with consistent user identity

More from Monday 28 September →