Subscribe RSS Feed | Follow on Twitter

VMware View Client vs. Citrix XenDesktop Receiver on an iPad

with 4 comments

Similar Posts:

Written by Christoph Harding

September 29th, 2011 at 8:46 am

Posted in Video,View Client,VMware View

Tagged with , , ,

«
»
  • Iguy

    What was used in this test? What was the configurations.

  • Tech

    My experience in real word is opposite…This test is not valid.sorry…

  • VDI_Man

    Devil is in the details on this one, don’t be fooled.

    Remember the iPad has no multimedia offloading capabilities, which prevents Citrix from shining through. Because of this lack of offloading on the iPad, all of this rendering/processing is occuring server side, greatly impacting user densities and scalibility.

    Meaning you need to buy more servers to accomidate multimedia with View or buy their forthcoming PCoIP card which is only in PCIe format with no OEM’s picking this up as a blade mezzanine – useless.

    Now the majority of iPad users are not going to connect to a virtual desktop to surf the web or to watch a movie when they have an iPad that can do that natively, why do you need the extra step? So is this a really valid use case, no.

    Does VMware beat Citrix now on this release… still the answer is no!

  • Matais

    VMware has gotten very good at showing
    their technology in single use cases and small densities.  Though this demo looks very impressive, we
    all know that VMware cannot scale this solution to anything significant.  Just investigate where all the
    large-scale deployments of VDI (thousands of implemented seats) are, do they use View or
    XenDesktop?  Since VMware can’t honestly tell
    anybody how to scale View, every medium to large organization that has
    tried in good faith, and has either fallen on their face or is dealing with a management and
    infrastructure nightmare.  There is no reason to fall for these small demos that
    are really just eye candy and useless in the real world. 

     

    This demo does a great job of showing
    what the PCoIP protocol can do if a single iPad is the only device talking on
    the network, but what does it look like on a real network with many devices?  What happens to the applications that the
    user interacts with while many session traverse the network?  Not to mention any normal network traffic from any other application or service.  Anybody who knows
    anything about TCP/IP will realize that UDP based real-time protocols need
    special care to deliver performance.  How
    do you optimize PCoIP so that the packets don’t get dropped when TCP based
    traffic occurs.  How do you dial in the user experience to behave in many different conditions?  When things as simple as a
    file copy from one device to another will cause UDP to drop, how do you prevent it from degrading PCoIP user experience?  When a user interacts with applications in a
    PCoIP desktop, perhaps clicking and moving window or typing something in an
    application, what happens when small bursts of TCP activity occur during those
    moments?

     

    Hopefully people out there aren’t
    making decisions on their VDI solutions based on these “smoke and mirror”
    demos.   When investigating a VDI solution,
    you should consider many different things, like vision of the company, ability to deliver at scale,
    and the ability to get the users to adopt the technology. 

     

    I’m certainly not going to bet my
    future on just VDI.  If looking for a
    pooled desktop, why count on linked clones and the building block
    infrastructures that VMware tries to sell today.  Without the ability to intelligently load
    balance the users to the modular blocks you build, it will become your worst
    nightmare.  Try offline desktops for more
    than 20 people, try pooled desktops for more than 750 desktops.  You will learn what you’re really getting
    into.

     

    BTW, both Citrix and VMware will
    eventually figure out how to offload H.264 and deliver a great user experience
    to any device with HTML5.  The question
    your have to ask yourself, is who is going to be able to do it at scale, with
    the greatest ease of management?  You
    will need to deliver the most flexible solutions with not only future
    application and desktop delivery technologies, but the legacy technologies we
    will all have to figure out how to continue delivering.