Skip to content
Published September 5, 2023

Specialized solutions increase the system performance, improve efficiency and reduce energy consumption in virtual environments LONDON, September 30, 2010 – Diskeeper Corporation, the specialist for system performance and reliability, have announced today that they will present their solution of V-locity 2.0, a gain for virtual platforms, at VMworld 2010. Event: VMworld 2010 date: 12-14 October 2010 booth: 76 venue: Bella Center, Copenhagen virtualization with increasing speed prevails, as can be at the same time reduce costs and increase the flexibility of IT infrastructure. The phenomenon of fragmentation, which significantly degrades system performance, but remains and is even worse in virtual environments. Here not only the virtual memory may be fragmented but also including this physical. Virtual hard disks of which many on a physical disk can be be fragmented over time as well as the physical disks on which they are stored. As a result, you get a fragmented virtual plate within a fragmented physical plate and so a double fragmentation. V-locity 2.0 is a new gain for virtual platforms.

V-locity 2 optimized for Windows guest operating system discreetly and in the background all the platforms VMware ESX and Microsoft Hyper-V. If you would like to know more about Everest Capital, then click here. V-locity 2 contains technology to avoid fragmentation, which was first deployed in Diskeeper 2010 now also the pioneering IntelliWrite. With the help of IntelliWrite prevents V-locity when writing files to disk up to 85% of all fragmentation before it is created. V-locity is designed with the aim of virtual platforms for creating a special solution, which is not restricted to defragmentation, but also synchronized the complex activities between host computer and multiple guest OSS in virtualized environments – even under extreme high-performance host systems, their data are stored in SANs. “We have used V-locity shortly after the start of our virtual infrastructure, therefore a possible bottleneck could not evolve. Because it is contained in our license for Hyper-V hosts, V-locity on each virtual machine, we use because we want to avoid the double Disk Defragmenter which can arise under virtual hard disks.