Extremely slow Git operations (commit, push, pull) in Studio Pro 11.14.0

0
Hi Mendix Community, I am currently working with Studio Pro version 11.14.0, and I've noticed severe performance issues with Git operations. Whenever I perform basic version control tasks inside Studio Pro, the process takes significantly longer than expected: - Committing changes takes an unusually long time to complete. - Pushing changes to the remote repository lags heavily. - Pulling latest updates exhibits the exact same sluggish behavior. Has anyone else experienced this performance drop in version 11.14.0? Are there any known workarounds, configurations, steps to speed this up, or is this a known bug in this release? Any help or insights would be greatly appreciated. Thanks!
asked
2 answers
0

Hi Keuris,

I think this issue could be related to Git performance rather than Studio Pro alone. Since you are experiencing delays in commit, push, and pull operations, I would suggest checking a few things before concluding that it is a bug in 11.14.0.

Here are some things you can try:

1. Check repository size

If your project has been maintained for a long time, the Git repository might have accumulated a lot of history and large files. This can affect the performance of version control operations.

You can try running the following command from your project repository using Git Bash:

git gc

This performs Git repository housekeeping and optimizes the repository storage. Make sure Studio Pro is closed before running it.

2. Check network and proxy settings

Push and pull operations depend on communication with the remote Git repository. If you are working behind a corporate VPN, proxy, or firewall, it could be affecting the connection.

You can check whether the required Mendix Git endpoints are accessible, especially:

https://git.api.mendix.com/

If you are using a proxy, verify that Git is configured with the correct proxy settings.

3. Check antivirus exclusions

Sometimes Windows Defender or other antivirus software scans files during Git operations, which can slow down the process.

You can check whether adding appropriate exclusions for your Studio Pro installation and local project directory improves performance. Follow your organization's security policies before making these changes.

4. Compare local and remote operations

It would also be useful to identify whether committing locally is slow or whether the delay mainly happens during push and pull.

  • If commit is slow, investigate local disk performance, repository size, and antivirus scanning.

  • If push and pull are slow, investigate network connectivity, proxy settings, and remote repository response times.

5. Compare with another Studio Pro version

If possible, try performing the same Git operations on the same project using an earlier Studio Pro version.

This will help determine whether the slowdown is specific to 11.14.0 or related to the project or machine configuration.

I couldn't find a confirmed Git performance issue specifically listed in the Mendix 11.14.0 release notes. However, since all three operations are affected, it would be worth investigating both local Git performance and remote connectivity.

You can also refer to the official Mendix documentation:
https://docs.mendix.com/refguide/troubleshoot-version-control-issues/

Hope this helps!

answered
0

Hi Keuris,

Since commit, push, and pull are all noticeably slower in Studio Pro 11.14.0, I would recommend isolating local Git performance from remote Git communication before assuming this is a version-specific regression.

Mendix Studio Pro uses LibGit2 for local repository operations and Git CLI for remote operations such as fetch, pull, and push.

1. Compare Git CLI performance

Open a terminal in your application directory and run:

git status
git fetch
git count-objects -vH

Measure the execution time of each command.

  • If git status is slow, investigate local repository performance, file scanning, and disk I/O.

  • If git fetch is slow, investigate network latency, proxy configuration, and Git server communication.

  • If Git CLI is fast but Studio Pro remains slow, the issue may be related to Studio Pro's version-control integration or model-processing overhead.

2. Check repository size and housekeeping

Mendix documents repository growth as a possible cause of slow Git operations.

After ensuring that all work is committed and backed up, you can test:

git gc

Alternatively, clone a fresh copy of the repository into a new local directory and compare the performance.

Avoid manually deleting files inside the .git directory.

3. Check local environmental factors

Verify that:

  • The project is stored on a local SSD rather than a synchronized network folder.

  • Antivirus or endpoint security scanning is not introducing excessive delays.

  • The installed Git version meets Studio Pro requirements.

  • Corporate VPN, proxy, or TLS inspection is not slowing remote operations.

If security software is involved, coordinate any exclusions with your IT team.

4. Compare Studio Pro versions

If possible, reproduce the issue using a separate copy of the project with the previous working Studio Pro version, provided that the project model is compatible.

Do not downgrade the original project or open an upgraded project in an incompatible Studio Pro version.

If Git CLI performance is normal but the slowdown occurs only in Studio Pro 11.14.0, this would provide useful evidence of a possible regression.

5. Collect Studio Pro diagnostic logs

Navigate to:

Help → Open Log File Directory

Collect log.txt and any relevant additional log files.

Record the duration of each operation and raise a Mendix Support ticket if the slowdown is reproducible.

The Studio Pro 11.14.0 release notes mention a fix for concurrent Git operations causing an Index is locked error, but that does not establish that the reported performance issue is the same problem.

Official references:

My recommendation: Start with the Git CLI timing comparison and a fresh clone. If both perform normally while Studio Pro 11.14.0 remains slow, report the issue with the timings and Studio Pro logs so Mendix can investigate a possible regression.

Hope this helps! If you find this answer helpful, please mark it as the accepted answer.

answered