Patriot SSD 64GB Review


Recommended Posts

SSDs right now are not great for anyone. The price/performence is just not worth it.

Also, the brands are not the same; Seagate/WD rule in the magnet deparment while it seems Patriot rules in the flash deparment.

Its gonna be a few years (Id even say 5) until SSD drives become standard (not to mention the size limitations right now)

SSDs right now are not great for anyone. The price/performence is just not worth it.

Also, the brands are not the same; Seagate/WD rule in the magnet deparment while it seems Patriot rules in the flash deparment.

Its gonna be a few years (Id even say 5) until SSD drives become standard (not to mention the size limitations right now)

Size isn't much of a problem for me to be honest. I have a Data hard drive which keeps all the files I use. My current RAID-0 array is my Operating System only.

Found some wierd stuff out, I formatted the SSD's in 4KB allocation units (not even what is recomended!) instead of 512byte and a lot of the lock ups went away... go figure... but ontop of that I did lose about 10% of the read speed, and write speed went down to a little below what the 2 HDD's in RAID0 was

? Sequential Reading ? 157.0 MB/ps

? Sequential Writing ? 68.20 MB/ps

? Random 512KB Reading ? 137.90 MB/ps

? Random 512KB Writing ? 35.90 MB/ps

? Random 4KB Reading - 14.71 MB/ps

? Random 4KB Writing ? 1.81 MB/ps

when you say MB/ps is that for pico seconds? cause that's really fast... if it's for per second then then you don't need the " / " sign per means divide in this case....

Sorry I am a nerd and these things catch my eye.

when you say MB/ps is that for pico seconds? cause that's really fast... if it's for per second then then you don't need the " / " sign per means divide in this case....

Sorry I am a nerd and these things catch my eye.

That's an average of sustained speeds

  • 2 weeks later...
Found some wierd stuff out, I formatted the SSD's in 4KB allocation units (not even what is recomended!) instead of 512byte and a lot of the lock ups went away... go figure... but ontop of that I did lose about 10% of the read speed, and write speed went down to a little below what the 2 HDD's in RAID0 was

Do you think the OCZ V2 SSD's would work like the Patriot SSD's if I used a RAID controller with onboard memory?

That's an average of sustained speeds

Hey I loved your review, it actually sealed my purchase on two of these, couldn't pass up the price.

I have them running in raid 0 right now and they are very fast, however I'm only getting like 160MB/s read. Is it because I didn't use the same stripe size as you did? Would changing the stripe size allow me to reach up to the same read speeds you were getting? Also I didn't specify any particular format size either. Currently I haven't noticed any studdering, which was the only thing I was worried about before getting them. Have you tried multiple formats and stripe sizes, and found the best one? Sorry for the bombardment of questions, but any input would be greatly appreciated!

  • 3 weeks later...

Excellent review, in-depth and informative. I was waiting for a real person to deliver some test results along a review for the new SSD's. Once SSD fixes it's little quirks and expands to 1TB or larger, then I'll make the switch.

Although, having a dedicated SSD solely for virtual memory would be very interesting to test...

  • 1 month later...

I got this thing!

~ 120MB/S Read

~ 0.3 Ms seek

But, it does get stuck sometimes. Gaming loading times are much better.

Performance is better but as I take it due to the method Window uses to write files, it's performance actually might suffer, so any application like O&O for example, to maximize the performance?

Defragmentation software would not help. Regardless of what the fragmentation software tells the SSD to do, the SSD will not listen. For example, if the software tells the drive to make a copy of [File Part Two] directly after [File Part One] and then delete the old copy, the SSD will receive the command but will make a copy of [File Part Two] at a random location to prevent wear-and-tear on the drive, rather than making a copy where it was told to make it. In all likelihood, the file will remain fragmented, but the drive will tell the defragmentation software, "I did what you asked", and the defragmentation software will think it accomplished something when it actually didn't.

  • 5 months later...

I heard Windows 7 RC builded with TRIM (SSD Command). Does anyone know if the Patriot SSD 64GB needs a firmware upgrade to utilitize the TRIM on Windows 7 RC?

I am going to setup a previously used Patriot SSD 64GB in a new HP Mini 2140 on Windows 7 x86 RC platform. Do I need to wipe it clean with a SSD erase tool before the re-install to claim all the memory back? If so, which one should I use? Anyone has any other advice?

Edited by vto
I heard Windows 7 RC builded with TRIM (SSD Command). Does anyone know if the Patriot SSD 64GB needs a firmware upgrade to utilitize the TRIM on Windows 7 RC?

I am going to setup a previously used Patriot SSD 64GB in a new HP Mini 2140 on Windows 7 x86 RC platform. Do I need to wipe it clean with a SSD erase tool before the re-install to claim all the memory back? If so, which one should I use? Anyone has any other advice?

probably should have started a new thread for this, but no, you dont need any "SSD Erase tool." it works just like a normal hard drive.

windows 7 does support the TRIM command, but i have no idea if this drive does, or ever will, support it. check the drive's website.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Turbo Pascal was my first real programming experience more than 30 years ago at university. I mostly taught myself from the included examples and help documentation, because the university only taught the basic syntax and philosophy of Pascal, without going deeply into Turbo Pascal’s advanced features. I still remember when I discovered that I could embed assembly language directly into Pascal code, call BIOS functions, manipulate screen memory, use mouse interrupts, and control peripherals from my programs. That opened huge doors for me. Programming back then felt really fun, direct, and close to the machine. What I loved about Pascal was its readability and the almost instant compile time. Turbo Pascal was an amazing environment, but unfortunately Turbo Pascal for Windows 3 did not feel like it fully carried that legacy forward. Later, Delphi got things back on the right track after the messy transition to TP for Windows. Sadly, Delphi suffered from years of uncertainty as it moved from Borland to CodeGear and then to Embarcadero. That instability made many developers lose confidence in it, even though Delphi itself remained a powerful and productive tool. I still work with Delphi from time to time, but I definitely miss the old days of Turbo Pascal.
    • I hope this encodes in to AV1 or AV2 as currently tiktok uses h265 and h264.
    • Qualcomm reportedly in talks to build custom video chips for TikTok parent ByteDance by Karthik Mudaliar Qualcomm is reportedly in advanced discussions to provide custom chip-design services to Chinese tech giant ByteDance, the same company behind TikTok. According to a report from Reuters, Qualcomm could be involved in designing custom silicon tailored for ByteDance's massive data-center workloads. If it goes through, the deal would make ByteDance one of Qualcomm's early anchor customers for its fastly growing custom chip-design division, For years, Qualcomm was the king of making smartphone processors and modems. The company has also been moving into the PC ecosystem and other formats such as on-device AI for Android XR headsets. However, this particular deal is about Qualcomm's custom Application-Specific Integrated Circuits (ASICs). For a platform like TikTok, ByteDance needs hardware that can help it ingest, process, and serve billions of short-form videos daily. Generalised hardware is no longer the most cost-effective and efficient route, which is why ByteDance is trying to develop custom Video Processing Units (VPUs). VPUs designed specifically for ByteDance’s algorithmic needs could drastically reduce data-center power consumption and improve encoding speeds at an unprecedented scale. The underlying tech behind these processors is actually from Qualcomm's recent acquisition of AlphaWave Semi, a high-speed connectivity specialist company. By combining AlphaWave’s high-bandwidth IP with Qualcomm’s architectural expertise, the company could begin mass production by the end of 2026, if the talks go through. All this also comes at a time when U.S.-China tech relations have dwindled. Escalating trade frictions between Washington and Beijing have severely impacted the export of high-end AI chips from U.S. firms like Nvidia, AMD, and Lam Research. Yet, the Qualcomm-ByteDance discussions show that U.S. tech companies are still actively seeking growth avenues and are open to doing business with China, where regulators still permit. Reuters notes that the outcome of this deal could be uncertain, and ByteDance might also seek partners other than Qualcomm. via Reuters | Image via DepositPhotos.com
  • Recent Achievements

    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      456
    2. 2
      +Edouard
      164
    3. 3
      PsYcHoKiLLa
      117
    4. 4
      Michael Scrip
      83
    5. 5
      Xenon
      69
  • Tell a friend

    Love Neowin? Tell a friend!