I am pleased to announce the release of CygNet 9.4! CygNet 9.4 has been in development since July 2019 and has a lot of new features that I am excited to bring to your CygNet deployments. Also, as a part of this release, we have transitioned to a new documentation delivery platform and have video content ready for you as well. Keep reading below for more details!
Citrix is a great way to serve up clients to your ever-growing sea of CygNet users. We know of many CygNet installations that utilize Citrix, but more recently we’ve run into some interesting issues revolving around the Citrix, Microsoft, and CygNet relationship. Some recent reports have come in with the mistaken impression that CygNet and Citrix aren’t compatible, and that installing CygNet clients will destroy your Citrix instance.
If your production database is larger than 500 Gb, I’d like to take a moment to talk about a potential ticking time bomb that might be present in your production environment so that you have the tools necessary to disarm it before it detonates.
Extreme file fragmentation + Small disk allocation size = Disaster
Do you know how to tell if the cache on your machine is being used properly for your CygNet services? What are the effects of a rampant cache growth? We in CygNet Support have not only had to troubleshoot these issues, we’ve also found the tools needed to diagnose and fix these issues.
Here is a scenario that I’ve seen crop up several times in the last few months:
A point enters the alarm state and an SMS notification has been sent, but several hours later no one has acknowledged it yet. Investigation begins into this issue and I notice that the notification service (GNS) has logged a successful send to my field techs’ wireless carrier’s email address, there are no errors reported, but no one has responded to the callout. I call the tech and he says he never received the notification.
Recently, I was asked to assist with a customer support call regarding a poorly performing CygNet Studio screen. Having just participated in Dan Snyder’s CygNet Database Service Diagnostics and Performance Tuning breakout session at this year’s WESC, I felt more than ready to take on this challenge. Surprisingly, the actual diagnostic and remediation process required was much more involved than I expected. My hope is that by describing, over the next several posts, the detailed process I went through to decrease the screen load time from 30 seconds to 3 seconds, you may come to understand the nuanced considerations required to craft and verify the most efficient solution for your particular needs.
Enter your email address to subscribe to this blog and receive notifications of new posts by email.