Avid Amoeba

@avidamoeba@lemmy.ca · Joined ⁨Jul⁩ ⁨2023⁩

Replying to @⁨avidamoeba@lemmy.ca⁩

This shit is so over. This gang ain’t gonna collude on price with Micron. They’re in for eating Micron. First its market share, then its IP by buying it for pennies on the dollar.

Especially pay attention to the CCP’s directive to share IP among RAM manufacturers. They appear to be looking at this problem as a supply shortage of an essential component for the rest of the economy, which it is. But that also means they aren’t playing for profit.

posted in Technology

Chinese CXMT to Match Micron's DRAM Manufacturing Capacity This Year

A particularly surprising discovery is that CXMT is constructing its cleanrooms—where the actual silicon is produced—in just around 12 months, whereas the rest of the DRAM manufacturing industry typically takes 21-24 months, nearly a full year longer.

Finally, the report notes that the Chinese government is encouraging CXMT to transfer its DRAM technology IP to other Chinese DRAM manufacturers such as JHICC, Swaysure, and YTMC’s subsidiary XMC. This initiative aims to alleviate memory shortages domestically before CAMT-designed DRAM enters other markets, such as the EU and possibly even the U.S.

www.techpowerup.com/350726/chinese-cxmt-to-match-microns-dram-manufacturing-capacity-this-year
TechPowerUpChinese CXMT to Match Micron's DRAM Manufacturing Capacity This YearChinese memory giant CXMT has been expanding its capacity so rapidly that the company is now able to compete with one of the largest memory manufacturers in the world—Micron. According to analysis from Citrini Research and their proprietary data, CXMT is projected to produce about 350,000 DRAM...

posted in Selfhosted

Improve very slow library scans on Jellyfin 10.11 / 12 on spinning media

I’ve been trying to upgrade from 10.10 to 10.11 for a while now, as the Android TV app keeps nagging me, and every attempt ended with impossibly long library scan times.

After some thorough investigation, it appeared that a Home Videos type collection causes unending scan (yet to be solved), but also that Jellyfin does a lot of writes to the config directory (either database or metadata or both). Mine’s on spinning media part of a ZFS pool. I tried a few performance tuning options, such as testing the config dir with recordsize (similar to block size) of 4K, 8K, 64K, 128K and library scans fell from 30-40 minutes down to 8-13min with 4K-64K. The ZFS tuning wiki suggest 64K recordsize with LZ4 compression for SQLite workloads such as Jellyfin. That seems to work as well as 4K and 8K but likely is faster when reading thumbnails and such.

Note that upgrading to 12-rc3, which is supposed to speed up library scans did not improve scan times for me. Optimizing config/database write speed did. I cross-checked the culprit by experimenting with moving the config dir to NVMe and RAM. Both of those got the scan times down to 8-9 minutes compared to the optimized spinning media’s 12-13.

So if you had upgraded (or about to) to 10.11 your library scans are (about to get) dog slow and your Jellyfin’s config dir resides on spinning media, optimize its write performance for SQLite.