Hi,

Slow commits and pulls in Studio Pro almost always come down to repository size, and the root cause is how Git interacts with the Mendix model format.

Why it happens

In the classic format, your whole model lives in a single binary .mpr file. Git is built around text deltas: for text files it stores small diffs between revisions. For a binary blob, a small change in Studio Pro can rewrite large parts of the file, so the stored deltas are much bigger. Over months of commits the object store in .git/objects/pack grows steadily. Every pull, push and especially clone then has more data to compress, transfer and unpack.

Common things that make it worse:

• Large binaries committed to the repo (PDFs, videos, zips, big JARs in userlib)

• Frequent re-importing of modules (a module-import-heavy workflow inflates the model history quickly)

• Lots of stale branches and deployment tags

• Loose objects and unreachable garbage that Git never cleaned up

What you can do (cheapest first)

1. Optimize repository storage. Go to Version Control > Optimize Repository Storage. This runs git gc under the hood, which repacks objects and prunes unreachable ones. Also enable Preferences > Version Control > Enable automatic repository optimization so this keeps happening.

2. Check your environment. Studio Pro is very sensitive to disk I/O. A project folder on a network drive, a synced folder (OneDrive), or a slow VDI disk will hurt every Git operation. Antivirus real-time scanning on the .git folder is another frequent culprit, so exclude your project directory if your policy allows it.

3. Keep binaries out of the repo. Review your .gitignore and don’t commit generated or large static files.

4. Clean up branches and tags you no longer need.

5. Use a partial clone when downloading the app (available since 10.12). It fetches the full content of the current revision without the full history, which makes clones much lighter.

6. Consider MPR v2 if you’re on a recent version. It splits the model into many smaller files instead of one monolithic binary, which plays much better with Git’s delta model.

7. Last resort: history cleanup. If the repo is already huge (several GB), Mendix provides a cleanup tool called git-fixer that wipes history down to the latest main commit. Be careful: other branches are removed, and teammates need to reset their local copies. Coordinate with the team, merge or back up branches first, and keep the backup it produces.

The Troubleshooting Repository Size page in the Mendix docs describes how to analyze which unit types are bloating your model. It’s worth a look before doing anything drastic.

Hope this helps!

Fjordi

Hi Carlos,

Mendix officially documents that slow commit and pull operations can be related to repository growth, Git performance, or network connectivity. I recommend checking the following in this order:

1. Check network connectivity

Ensure that home.mendix.com, cloud.mendix.com, and git.api.mendix.com are accessible over HTTPS (port 443). If you are behind a corporate firewall or proxy, ask your network administrator to verify that these connections are not being blocked or interrupted.

2. Check repository size and Git performance

Large .mpr files, large files committed to version control, and frequent module reimports can increase repository size and slow down version-control operations.

Refer to the official guide:
https://docs.mendix.com/refguide/troubleshoot-repository-size/

3. Check the Git proxy configuration

If you use a corporate proxy, verify the Git proxy configuration. Mendix documents that Git for Windows may not automatically use the system proxy settings, which can affect remote Git operations.

Official guide:
https://docs.mendix.com/refguide/troubleshoot-version-control-issues/

4. Check Studio Pro logs

In Studio Pro, open Help → Open Log File Directory and inspect log.txt for connection timeouts, SSL errors, proxy errors, or Git-related exceptions. These messages can help identify the actual cause.

Official guide:
https://docs.mendix.com/refguide/troubleshoot-team-server-issues/

5. If the issue persists

Check whether the slowdown affects all team members or only one machine. If it affects everyone, investigate repository and network-related causes. If it affects only one machine, focus on its network, proxy, disk performance, and local environment.

If you share the relevant error from log.txt, along with your Studio Pro version and whether the issue affects other team members, it will be easier to narrow down the root cause.

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

Hi Carlos,

Slow commits and pulls in Mendix are almost always caused by the size and condition of the Git repository, not by the code you’re changing. Here are the main causes and how to fix each one.

1. Large repository (main root cause)

• Issue: Git can’t efficiently store small changes to the binary .mpr file. A small microflow change can add a megabyte or more to the repository, so it grows quickly over time and every commit or pull gets slower.

• Fix: Check the repository size on the Team Server page in the Mendix Portal. If it’s very large, see Mendix’s Troubleshooting Repository Size guide. It covers the git-fixer cleanup tool.

2. Old MPR storage format

• Issue: The old MPRv1 format stores the whole app in one file, which makes the repository grow fast.

• Fix: Make sure the app uses MPRv2. From Studio Pro 10.22, conversion happens automatically when opening the app. On 11.14 you should already be on MPRv2, but apps carry over the history from before the conversion.

3. Repository not optimized

• Issue: Loose Git objects build up and slow down operations.

• Fix: Make sure automatic repository optimization is enabled in Studio Pro preferences. You can also run git gc in the app folder to optimize it manually.

4. Clone type

• Issue: A full clone downloads the complete history, which takes longer for large repositories.

• Fix: Consider a partial clone. Mendix describes it as faster to clone and using much less disk space. The setting applies to new downloads only, so you’d need to re-download the app.

5. Antivirus scanning

• Issue: Antivirus software scans every Git file during commit and pull, which slows them down a lot.

• Fix: Exclude the Mendix project folder and Studio Pro from real-time antivirus scanning. Mendix has an Antivirus Exclusion guide for this.

6. Network and environment

• Issue: Slow internet, VPN or proxy, or slow disks (network drives, OneDrive or other synced folders).

• Fix: Keep the project on a local SSD outside synced folders, and test without the VPN if possible.

7. Committing too many changes at once

• Issue: Large, infrequent commits transfer and merge more data.

• Fix: Commit and pull smaller changes more often.

Quick checklist

1. Check the repository size on the Team Server page.

2. Enable automatic optimization, or run git gc.

3. Add antivirus exclusions.

4. Move the project to a local, non-synced folder.

5. If the repository is still large, use a partial clone or the git-fixer cleanup.

Hope this helps! If this solution works for you, kindly mark it as the accepted answer so it can help others facing the same issue.

Sources to analysis:

• Troubleshooting Repository Size – Mendix Docs

• Selecting the Clone Type – Mendix Docs

• Version Control FAQ – Mendix Docs