Plextor first showed off the M7e at CES earlier this year and at Computex we got an update on the release schedule. Plextor is now aiming for Q3 release, meaning that we will likely hear the final release at Flash Memory Summit in August. Specifications have not really changed since the M7e still utilizes the same Marvell PCIe 2.0 x4 AHCI controller with performance rated at up to 1.4GB/s read and 1GB/s write as well as up to 125K random read and 140K write IOPS. M7e will be available in both M.2 and PCIe card form factors with capacities range from 256GB to 1TB, so the M7e may very well be the first M.2 2280 drive to break the 1TB barrier. 

Regarding the TLC drive M6V (or M7V as Plextor now calls it), Plextor is taking its time to fine tune the firmware to squeeze every megabyte of performance out of the drive and more importantly ensure high reliability and endurance. Plextor told me that its firmware can boost the endurance to 2,000 P/E cycles with 15nm TLC, so it the claim holds true then I'm fine with Plextor taking a little longer and pushing the release to 2016.

On the software side, Plextor actually had three new items to show. The first one is updated PlexTurbo, which now carries version number 3 and increases the maximum cache size to 16GB. The cache size is also now user adjustable and supports multiple disks, so one can decide what Plextor SSD to speed up with PlexTurbo.

The first new addition to Plextor's software suite is PlexVault, which creates a hidden partition for storing sensitive data. The partition is completely hidden and isn't even visible in Disk Management, so other users won't even know that such hidden partition exists. Accessing the partition works through a hot key, although a password can also be entered to protect the hidden partition from accidental access. I'm not sure how useful the feature really is, but I guess it creates another layer of security for NSFW (not safe for the wife) content for those who may need it. 

The final piece of new software is PlexCompressor, which is an automated compression utility. If a file is not accessed for 30 days, PlexCompressor will automatically compress the file to increase free space. The file will then be uncompressed when accessed, which obviously takes a bit of the free space since the file will now be stored in uncompressed format for another 30 days. The compression is transparent to the user and is done fully in software (i.e. by the CPU), so it's not SandForce-like hardware compression. There is no impact on SSD performance, although as compression consumes some CPU cycles there may be impact on CPU heavy workloads and especially battery life. Out of the three pieces of software Plextor has, I think PlexCompressor is the most potent because it results in concrete extra free space for the end-user and with SSD prices still being relatively high (compared to HDDs) it makes sense to get the most out of the storage one has.

Comments Locked


View All Comments

  • icrf - Thursday, June 11, 2015 - link

    I figure I'll pick up an sm951 when xeon-d shows its face in a little more volume at more reasonable price points. That will be the trigger that lefts me shift hardware around to different tasks (it's a little convoluted). I expected it to happen by now, but if it takes much longer, the sm951 may no longer be the best bet around. At best, maybe the nvme version of the sm951 will be it, but I don't know that it'll be meaningful for client workloads (on x99, so spare cpu cycle abound).
  • Ethos Evoss - Sunday, June 21, 2015 - link

    man the price , all is about the pric e.. because in real use there will be no difference .. using these high end PCI-e SSDs .. In windows use it will be just no difference AT ALL
  • stephenbrooks - Thursday, June 11, 2015 - link

    I wonder if the compression can increase the effective bandwidth, since the data is going through the controller and PCIe bus compressed, only being decompressed on the CPU?
  • Gigaplex - Thursday, June 11, 2015 - link

    It's stored uncompressed originally, so there's no bandwidth savings there. When the file stagnates, the software will compress it, requiring a decompressed read, a compressed write, and a delete/TRIM. That will consume bandwidth, hopefully when idle. When reading the file, that's a compressed read, followed a decompressed write, so there's no bandwidth savings there either.
  • 'nar - Sunday, June 14, 2015 - link

    'Barrier' Who said that 1TB was not possible? That it was a "barrier?" The sound barrier was actually thought to be just that. Scientists and Engineers thought that Chuck Yeager's X1 might break up before ever crossing the sound barrier. The sound waves create a wall that they did not know how, or if it could be breached.

    More and more in recent times technical milestones have been characterized as barriers. They are not. Milestones, Thresholds, Limits(as in former limits), these are all reached, breached, or surpassed. Not barriers.

    Barriers are used like metaphors. They are lies that give the sentence a stronger impact. Unlike metaphors, this is not a comparison. Metaphors add feeling, flair, and substance. But again, who ever said that 1TB was not possible? Where is the wall? Where is the technical limitation? That description is inaccurate.

    But I guess kids these days just think that it is "sick."
  • TheinsanegamerN - Monday, June 22, 2015 - link

    Agreed. Apple has had a 1tb M.2 style drive for two years, and both 2.5 and msata drives had 1tb versions. Sounds to me like OEMs are trying to come up with reasons to charge more...

Log in

Don't have an account? Sign up now