![epic hyperspace epic hyperspace](https://i0.wp.com/erickimphotography.com/blog/wp-content/uploads/2018/06/2001-space-odyssey-cinematography-698.jpg)
Should we be looking in that direction?Īpologies for the long rambling post. We aren't doing any GPO/DEM tasks to throttle/optimize Blast really, it's just vanilla out of the box. We've also basically just gone with Blast canned. Our network is, from a speed/latency perspective, pretty solid I'd say. The Blast part has me a bit concerned, as that was one of the changes that also went in. We can't go anywhere with the Horizon client on ThinOS, as I said we're at the latest. We've pushed a couple firmware updates out, but, no real reports yet good or bad. We recently excluded the actual Epic.exe file from any kind of scans in Deep Security, that we're using for Anti-Malware protection. While this has been getting looked at from the Epic side, we have done some steps on our side. And yes they have started to direct us to go in a published app direction, Citrix or RDSH. Doesn't sound like much, but, according to Epic, what we see on the better 8280s is still actually higher than they prefer, so, that makes the 8180s look that much worse. I mean we're talking a good 7% or 8% higher hit on the 8180s vs. the 8280 process doesn't SEEM that much better. Someone can correct me, but, the 8180 processor vs. So far, no luck from Epic to isolate a workflow. I say that because the pools on the 8180 are our clinical Doctor/Nurse kiosks, where as on the 8180 we're offering a generic remote access desktop for remote users. The problem is the workflow could be very different, so, we're having Epic dig in further there to see if they can drill down to a specific workflow causing the hit. I don't know how confident I feel this is the case, but, it's what we have.įrom the Epic side of things inside system pulse (their performance console), we see a definite increase on response time on the pools that are on the 8180s vs. The rest of the VM performance apparently is fine. Since this has occurred, we have gotten consistent complaints about performance, which we believe is isolated into Hyperspace.
Epic hyperspace upgrade#
We are 100% vSan all flash on the storage end, dedup and compression is enabled.Īround the same time as we did the most recent upgrade to May 2020, we also migrated the rest of the VDI environment to Windvia Blast (from Windows 7 via PCoIP).We are deployed on Dell R740XD hosts, with a mix of 81 chipsets.We reserved all 6GB of memory on the VM parent before deployment. Our deployment is configured as 3 vCPUs and 6GB of memory per instant clone VM.I didn't see anything in the release notes for the later releases that caught my eye for the issue I'll be describing.
Epic hyperspace code#
The client is the latest offered by Dell, the OS code is about 3 versions behind.
![epic hyperspace epic hyperspace](https://i3.ytimg.com/vi/gKTQVsQvwp0/hqdefault.jpg)
We are currently running Epic Hyperspace May 2020 on our VDI environment, locally installed in the parent image.This goes out pretty much exclusively to my fellow members of the Healthcare community.