On May 16, 2014, Oracle entered into an agreement to acquire GreenBytes, a provider of ZFS technology, for an undisclosed price. In addition to expertise in areas related to ZFS, GreenBytes has developed a deduplication, replication, and virtualization overlay for it. (Rather bizarrely, in a tussle with the then-giant in 2009, GreenBytes accused Sun of stealing its deduplication technology.)
Articles Tagged with GreenBytes
There is a new set of tools available for Caching up and down the stack which we covered within Caching through out the Stack, however in reality where is the best place to cache data for your application and what are the ramifications of using such a cache. Recently, we had a caching problem, actually two of them. Both caused by the same thing, a lack of full understanding about what was being cached. For any application, the best way to cache is to cache in memory as close to the application stack as possible, which in our stack could be within the application, the OS, or even a hypervisor based disk cache. However, which does your application actually use?
One sure way to improve performance is to cache the non-dynamic data of any application. We did this to improve the overall performance of The Virtualization Practice website. However, there are many places within the stack to improve overall performance by caching, and this got me to thinking of all the different types. At the last Austin VMUG, there were at least three vendors selling caching solutions that were designed to improve overall performance by as little as 2x to upwards of 50x improvements. That is quite a lot of improvement in application performance. Where do all these caching products fit into the stack?
Participate in any virtual desktop design session and you will know that the discussion almost always moves immediately to how many IOPS per virtual desktop session should be expected. More often than not, the leader of these conversations will answer “it depends”. This is a statement that does not give most end users a warm a fuzzy feeling because it usually comes with a pretty heavy storage price tag. Unfortunately, there are many factors that affect overall performance. Within the virtual desktop session, the number and type of applications you have running, the layers of security configuration and policy that are applied, and how you are handling user personalization have an impact on IOPS. Many of these challenges can be addressed by applying good standard virtual desktop practices, which are often different from the way physical desktops are traditionally architected.