PCS Response Concerns

[reusable_arch_ftw]

Hello! First post to the forum and hoping to glean some insight from the wealth of expertise here.

Current running on-premise configuration with PCS & Prolaborate Apps hosted on single server separated by port in our Dev/Test environment. Database server for both is a separate machine. Response times (Ping) to the PCS/Prolaborate app server are <=10ms while directly on the Apps Server or device on corporate LAN with 146ms for remote/telework employees. Response time using "ProCloud Server connection" via EA Client's Help GUI adds an additional 200ms even on the application server; around 230ms on the server/LAN client and 370ms for remote employees. No additional delay in Simple database query execution from that total. No issues on the Prolaborate web side for responsiveness or noticeable delay.

Would really like to figure out the expected behavior for PCS before we can promote to our production. Is this 200ms additional delay an expected behavior? The troubleshooting guide shows around 26ms for the ProCloud Connection tool response. As of now the basic authentication for Enterprise Architect client and generic simple modeling is painfully impacted. Any thoughts or perspective would be greatly appreciated.

Chris

[Guillaume]

Hi Chris,

Sounds like an infrastructure problem. I experienced similar issues with on site and remote access from EA and Prolaborate to the PCS worked fine until changes where introduced on the infrastructure (security, SSL certificate, antivirus, VPN client...).
Users complained EA became unusable when working from home. There was nothing I could do on the application ; IT department eventually sorted it but I don't have the details about what had been done.