If you are experiencing performance issues when working with Horizzon, Enterprise Studio Online (cloud solution) or Enterprise Studio in a hybrid solution (on-premise Enterprise Studio with a hosted Horizzon Server and web portal Horizzon) several factors may impact your experience. The main issue in such cases is network based (high latency between your computer and Bizzdesign's servers and/or insufficient bandwidth). For hybrid installations additional factors might impact performance.
First requirement for a good performance is having a fast internet connection, but there may be other factors negatively influencing the performance. The requirements for your internet connection are:
|Bizzdesign service||Bandwidth recommended per user||Recommended maximum roundtrip latency|
|Enterprise Studio Online||5 Mbps download / 1 Mbps upload||< 100 ms|
|Horizzon web portal||10 Mbps download / 1 Mbps upload||< 150 ms|
|Hybrid Enterprise Studio (locally installed client used with hosted server)||10 Mbps download / 3 Mbps upload||< 150 ms|
Symptoms of insufficient network performance
To measure the network latency from your browser to the Amazon Web Services™ datacenter where your Horizzon is located you can use CloudPing.info (https://www.cloudping.info/). This site allows you to perform an HTTP ping to measure the network latency from your browser to the various Amazon Web Services™ datacenters around the world. If you are not sure where your Horizzon is located, contact Bizzdesign for more information.
Symptoms in Enterprise Studio Online
Insufficient network performance in Enterprise Studio Online is typically noticeable due to mouse clicks and mouse movements being slower than expected, and screen contents taking a noticeable amount of time to update. The current network latency can be seen from within Enterprise Studio Online by clicking in the session toolbar, and then choosing Streaming Mode > Show Streaming Metrics. The Network Latency window should show values of less than 100 ms, When dragging an object on the screen as fast as possible the frame rate should be higher than 10 fps and bandwidth usage should peak at values over 1000 Kbps.
Symptoms in Horizzon web portal
Any lack of performance in Horizzon can be noticed in slow responses to mouse clicks and/or pages in the web portal taking a long time to load. This can be caused by either insufficient bandwidth or network latency that is too high.
Symptoms in hybrid Enterprise Studio
For users of a locally installed Enterprise Studio client insufficient network performance can be noticed in the following ways:
- Opening a model package for the first time takes a long time during the "retrieving contributions" step: this indicates insufficient download bandwidth is available.
- Dragging an object onto a view or modifying an object on a view causes the application to freeze temporarily the first time that view is changed, but not during subsequent changes to the same view. This is a sign of high network latency.
- Committing changes to Horizzon takes a long time. This is indicative of insufficient upload bandwidth.
Possible solutions for network performance issues
In order to improve the connection, check the following:
- Use of VPN connections
- Use of proxy servers
Using a VPN connection and/or proxy server is strongly discouraged. When using a VPN or proxy server, data traffic goes to your VPN/proxy server first and from there to Horizzon when working with the web portal. When working with Enterprise Studio, traffic goes to your VPN/proxy server first and only then to Horizzon.
To test whether leaving out a VPN connection or proxy server will improves performance, first measure the current network latency using the Cloudping tool referenced above. Then switch off one VPN connection or proxy server and measure again and see if there is any improvement. Do this for each VPN connection and/or proxy server you are using.
Other performance considerations for hybrid Enterprise Studio
Make sure your local system meets the System requirements for the Bizzdesign Horizzon platform. Apart from the CPU and memory requirements, the following factors have a large impact on performance:
- Never store the Team Data folder on a network drive.
- Make sure a fast local disk is used, both in terms of access latency and throughput (either SSD or NVME storage).
- Exclude the Team Data folder from any virus scanners/other security scanning tools.