Why is the Copia desktop app slow to render my PLC project?

The Copia desktop app is always "looking" for changes to files to the active repository that's located on your computer. The desktop app will attempt to render your PLC project changes as soon as you update and save a PLC project file and return to the Copia desktop app. Below are the general actions that occur when you do this:

1. The file is uploaded to Copia's backend servers (this is not the same as pushing a commit)
2. The file is "decompiled" or "converted" to a text-based format in order for Copia to detect the differences
3. The "converted" project is cached for faster loading in the future
4. The rendering of the changes is sent back down to the Copia desktop app

Typically, the biggest portion of the time spent loading in the desktop app is the time it takes for your project to get uploaded to Copia's servers. For example, if you have a 40 MB TIA Portal project and an upload speed of 10 Mbps, it will take ~30 seconds for the file to be uploaded. Improving your network's upload speed will reduce the time that it takes to see the rendering in the desktop app.

Another factor that affects the rendering time is the size and complexity of your PLC projects. Large projects with many programs, routines, tags, etc. tend to take longer to render.

Navigating away from the desktop app will stop the upload and conversion process. If you have an especially large project that is taking a while to render in the desktop app, we recommend that you commit and push immediately. Then you can view the commit in Copia and leave the tab open while the render occurs.

If you are experiencing unacceptably long rendering times on your projects, please submit a Bug Report.