Optimizing Performance in the Hosted Environment

There are a number of moving parts that make up the virtualized DESTINI solution including the client's infrastructure, the DESTINI suite, Beck Technology's cloud infrastructure, the public internet, and more.

The purpose of this article is to help clients understand what aspects of this broad infrastructure can affect the performance of DESTINI products, and how best to approach troubleshooting issues to achieve an optimal user experience.

Where to Start

When it comes to the topic of performance in the virtualized DESTINI solution, it's important to know that there are many moving parts. If performance is lacking, there is usually a 'typical' reason for the experience which helps start the conversations that will ideally lead to the quickest resolution.

Remember; these are good starting points - not a guaranteed solution.

• Slow Actions and Commands -- Look at how users are using the product
  • Example: Opening an estimate is slow
  • Example: Changing a value in the Estimate View is slow
  • Example: Running a report is slow
• Choppy Experience -- Look at the users' infrastructure
  • Example: Navigating BIM 360 isn't smooth
  • Example: Drawing shapes in 2D is slow
  • Example: It gets slower when more team members are using it.

Client Infrastructure

When users are experiencing "choppiness" in their usage of the virtualized DESTINI solution, the cause is most likely related to their infrastructure. This is not a guarantee and only intended to explain why this is the starting point for troubleshooting "choppy" user experience.

Bandwidth

On the surface, the network requirements for our cloud solution are generally pretty low. However, there can be moments where bandwidth required is high. To make this more challenging, when multiple users are working out of the virtualized DESTINI solution at the same time from the same location (eg. an office), the overall bandwidth requirements for the that team/office goes up.

Monitor resolution is also a major factor when considering how much bandwidth is required.

• 4K resolution: IT staff should be aware that anyone running a 4K resolution needs at least 15Mbps of bandwidth per 4K monitor they are using. This 15Mbps represents a peak bandwidth requirement.

• 1440p resolution (most common): IT Teams should be aware that anyone running a 1440p resolution needs at least 5Mbps of bandwidth per 1440p monitor they are using. This 5Mbps represents a peak bandwidth requirement.

• Lower resolutions: 1080p is the most common used after 1440p. We recommend the same 5Mbps bandwidth requirement as above.

Network

Most people connect to their corporate and home networks through Wi-Fi. This is typically out of convenience. Most home users have a single wireless access point. Most corporate offices have multiple wireless access points located throughout their office. Although convenient, Wi-Fi has a few potentials shortcomings:

• A wireless access point generally has lower bandwidth than the user's internet connection.
• A wireless access point shares its resources across all connected users.
• A wireless access point has a finite capacity, and it can be overwhelmed based on the demands put on it. Although it is more likely for a wireless access point to be overwhelmed in a corporate office due to the number of connected users, it is possible for a home user's wireless access point to be overwhelmed for the same reason.

Users in an office should ensure that their IT team is aware of the bandwidth requirements above and that the wireless access points are not being overwhelmed by the number of the connected users.

Client IT staff should troubleshoot Wi-Fi performance issues in a number of ways:

• Rather than connect to Wi-Fi, physically connect (aka hardwire into the network), and test for performance improvements in the application.
• Mobile devices can be used as a Wi-Fi hotspot and typically offer good connection performance (as well as a secondary connection with which to troubleshoot potential Wi-Fi issues).
  • A mobile device will struggle if the user is streaming audio or video through it.

User Computer

The user's computer represents 1/3 of the hardware involved in our virtualized solution. Although the virtualized DESTINI solution is running on a virtual machine in the cloud, the user's computer is ultimately responsible for "assembling" the video that is shown on the user's computer. This assembly takes processing power just like any other application.

If the client is experiencing a "choppy" experience, the user's computer could be factoring into that experience. Treat this like you would treat any experience you have with an application running slow on a computer:

• Restart. It's important for everyone to restart their computer on a regular basis. It's also important to make a distinction between a restart and a shutdown. In Windows 10+, a shut down no longer puts the machine back to a clean memory state -- you can verify this in Task Manager and looking at your uptime after doing a shut down. A restart will put the machine back to a clean memory state.
• Close applications that aren't necessary. Every application that's running on the computer is taking up CPU and memory. If you don't need to be using the application, close it down to free up resources for the other applications running on the computer.

Although it might sound silly, monitor resolution comes into play here. If the user is using 4K monitors and experiences video stuttering, we recommend trying a lower resolution. 

Verify if the user's computer meets the hardware requirements for running the DESTINI suite locally on their machine. This will help ensure the user's computer isn't underpowered.

Product Performance

When users are experiencing long wait times for the application to complete operations, the starting point for troubleshooting is the product.

Users should be aware:

• Launching DESTINI Estimator can take 60 seconds. This is normal. Estimator does a lot when it loads -- connects to a cost database, dynamically loads all of its views and modules, etc.
• Loading a typical estimate can take 30-60 seconds. DESTINI Estimator is an intelligent, tightly coupled platform that links a lot of data together. This takes time to open and hook up.
• Saving an estimate is dependent on how many changes there were since the last save and can take anywhere from 5 seconds to more than 30 seconds.
  • Remember that the counter on the save button is a guideline. It is intended to help the user understand how much data is being saved, but doesn't tell the whole story.
  • Some actions in Estimator modify a lot of data yet show a low counter (e.g. bulk modify line item, modifying a distributed fee, etc.).

There are some use cases for DESTINI Estimator that place a heavy workload on the application, and can significantly impact performance. Users should be on the lookout for these:

• Large number of WBS Properties
• Formulaic WBS Properties
• Formulaic Cost Properties
• Large number of Distributed Fees
• Complex Dashboards
• Complex Project Views

System Guidelines

We have basic system guidelines documented in the Help Center that can be used as a starting point for an individual user's machine.

• System Guidelines for DESTINI Products - Hosted Environment