nathanfries

The GB202 RTX 5090 was discontinued, which had 32GB of DDR7 and was subject to export controls. Coincidentally, the GB202 RTX Pro 5500, which has 84GB of DDR7 suddenly was able to be produced and is somehow compliant with the export controls.

I'm not sure how to square this against there not being some funny business with the export controls.

I think it was indeed the bottleneck, however the assumption that "coding is the bottleneck" was baked into how organizations were measured, optimized, staffed for the last couple of decades.

I noticed that too. I feel like this might be a new way of laundering AI written text, just provide the quote verbatim as if the they believe it was actually written by the author.

I similarly don't know much about motor control or hardware in general, but would this maybe open up multiplexing options?

I followed this line of thinking last week due to curiosity w.r.t ECS & SQLite. I found that the bottleneck was not on the reads, but on the complexity of the writes (iterating each entity and subsequently you have num_systems X num_components writes). You can actually avoid this entirely if you write your systems in SQL.

Since I had already thrown out logic & reason for the sake of curiosity, I took it a step further and learned that the Bun JS runtime actually has SQLite baked in, which allows you to create a :memory: db that can be accessed _synchronously_ avoiding modification of most ECS implementations. (I'm not familiar with the larger SQLite ecosystem, but being a largely TS developer this was very foreign to me)