On VC servers that have the most jobs and that use the most file reads, it is extremely slow when opening VC variables. It doesn't matter whether working locally on the server, or connecting over the port from another computer; or whether using a computer with additional memory. I would imagine that since the file reads max out the allowed amount of output on the server, then on VC servers that contain a relatively large number of jobs containing a relatively large number of file reads, then there is a lot being loaded each time the variables are accessed.

Do you have any ideas about how to optimize how VC is set up to minimize the length of time to open the VC variables? As far as the allowed output, it is set at the level needed to not truncate needed output for any task on the server, around 10K.

It is not concerning output but how many Jobs and Task. The reason is currently that we create a lot of subnodes. We will optimize this part soon. Thank you for the report.

---

Please try version 5.0.3. from the beta forum. We have made some adjustments regarding this.

---