(or Load balancing, or much larger storage, or wider performance)
Using a network file system/ block storage allows you to have HA disks. If you have a network file store, its almost always going to be slower than local storage (assuming using the same hardware) thats not the point. When you have VMware vcenter, the power is not in the inherent speed (its not the fastest) its the simplicity of creating a cluster. I would suggest that this is apples to oranges. Stuff like different defaults for fsync, “accidentally” using different block sizes on a RAID array / filesystem / NFS mount, forgetting to use the same write-back/through settings on both, etc. I don't like these terms but it's easy to understand why they became so common.ġ.
Apache or IIS that way and you'd have the average late-90s web server sales pitch.
That wasn't too bad because both were their own servers but if you imagine that they were comparing their shiny new server to e.g. It also helps to remember that VMware has been in the enterprise space for a long time and a lot of people in that field have been burned by benchmarketing where a competitor would run an ad campaign hoping nobody would notice that their big performance lead was due to misconfiguration.Įven now, where it's easier to check the details, it's fairly common to see things like the HTTP/2 demo from yesterday ( ) which overstated gains by misconfiguring the HTTP/1.1 server used for comparison. As wila noted, benchmarks are easy to get wrong.
0 kommentar(er)
