3PAR also includes a 400GB SSD encrypting drive at the same time while I do not see any mention of FIPS validation on that device.
Only a passive point out of this on the slide, very little in depth to report about, but I think The essential concept is instead of having asynchronous replication running on snapshots that kick off every few minutes (Probably each and every 5 minutes) the replication procedure would run a great deal more routinely (but not synchronous nonetheless), Potentially as Repeated as every 30 seconds or a little something.
Compression stays a street map product, They can be focusing on it, but certainly not All set for release nowadays. Also this marks possibly the main 3PAR hardware released in more than a decade that wasn't accompanied by SPC-one outcomes.
I am informed The brand new 20k collection is amazingly cost effective available in the market. The value level is significantly reduce than before technology high-end 3PAR techniques. It is really priced greater when compared to the all flash 7450 for example although not substantially additional, entry stage pricing is claimed to get in the $100,000 array, And that i heard a range tossed all-around that was lower than that.
HP touts the scalability of usable and raw flash capability of these new systems + The brand new three.84TB SSD versus their competition:
3PAR is the sole SSD Remedy above tested with four controllers(totalling four Gen4 ASICs, 24 x 1.8Ghz Xeon CPU cores, 64GB of information cache, and 32GB of Handle cache), meaning with their persistent cache technological innovation(which is bundled at no extra Value) you are able to get rid of a controller and retain a fully secured and mirrored generate cache.
engineering for Gen8 methods, even though they opted let alone much on this time close to. It is really anything I've hounded 3PAR to the past 4 decades to have going, I am absolutely sure They can be focusing on one thing......
I don't think any of one other units are even effective at this kind of configuration irrespective of Price.
If I remember the right way nearly 100% of your cache on the all SSD-units is publish cache, reads are seriously affordable so little caching is done on reads.
In past times 3PAR programs have been rather bandwidth constrained because of their utilization of PCI-X. Though the newest era of stuff (7xxx/10xxx) all leverage PCIe.
3PAR is effectively conscious of my ask for, so almost nothing new here. David did point out they do want to do this however, no Formal timelines but. Also it sounded like they won't go forward Together with the server-side SmartCache integration with 3PAR (I might fairly provide the cache in the array in any case and they appear to agree).
I like to compare the NetApp kind of clustering into a cluster of VMware hosts (in which the VMs might be the storage volumes).
I am not a hardware dude to this depth of course. But I did instantly acknowledge MSI-X from an extremely difficult troubleshooting process I went by several years back with some Broadcom community chips on Dell R610 servers (while The problem wasn't Dell precise). It ended up staying a bug with how the Broadcom driver was dealing with(or not) MSI-X (Redhat bug here).
They this link also pointed out that in the course of among the list of SPC-one checks (not sure if it was 7400 or 7450) among the SSDs failed as well as system rebuilt by itself. They said there was no important performance hit(as just one might expect offered encounter While using the technique) given that the test ran.