<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Samsung 990 PRO 2TB: Performance Degradation After 7B2QJXD7 Firmware Upgrade - Capacity-Specific Bug? in Monitors and Memory</title>
    <link>https://us.community.samsung.com/t5/Monitors-and-Memory/Samsung-990-PRO-2TB-Performance-Degradation-After-7B2QJXD7/m-p/3401375#M17618</link>
    <description>&lt;P&gt;"Does anyone have result performance before and after firmware update?"&amp;nbsp; Well, one can only hope so.&amp;nbsp; The difficulty, of course, is that, to my knowledge, there's no way to rollback the firmware version, so there's no way to readily repeat the experiment.&lt;/P&gt;&lt;P&gt;"It seems like everyone is pointing the issue towards the firmware, solely based on the fact that the firmware was the last thing that changed."&amp;nbsp; Fair enough, but, hey, isn't that the scientific method?&lt;BR /&gt;&lt;BR /&gt;"I am not seeing the same issue."&amp;nbsp; I understand -- although how much of the drive's capacity is used may also play a part (in my case, it's my system drive with 5 partitions, and total usage is ~55%).&amp;nbsp; Unfortunately, I'm using Linux, so I can't use Samsung Magician to assess performance -- another variable in assessing this issue.&lt;BR /&gt;&lt;BR /&gt;I repeated my initial post on Anandtech, trying to drum up more data.&amp;nbsp; My most recent post there provides a little more data as well as the fio commands that I'm using (see&amp;nbsp;&lt;A href="https://forums.anandtech.com/threads/samsung-990-pro-2tb-performance-degradation-after-7b2qjxd7-firmware-upgrade-capacity-specific-bug.2632571/#post-41530313" target="_blank"&gt;https://forums.anandtech.com/threads/samsung-990-pro-2tb-performance-degradation-after-7b2qjxd7-firmware-upgrade-capacity-specific-bug.2632571/#post-41530313&lt;/A&gt;).&lt;BR /&gt;&lt;BR /&gt;Note that the degradation in random write performance that I'm measuring isn't really perceptible -- if I weren't benchmarking after each major change, I wouldn't have noticed anything different.&lt;/P&gt;</description>
    <pubDate>Fri, 07 Nov 2025 17:54:15 GMT</pubDate>
    <dc:creator>SFdrifter</dc:creator>
    <dc:date>2025-11-07T17:54:15Z</dc:date>
  </channel>
</rss>

