Synapse workspace take longer to load and even while publishing takes longer

Surbhi Chaurasia 20 Reputation points Microsoft Employee
2025-02-20T07:55:35.47+00:00

I’m reaching out to report two issues we’ve been experiencing with our Synapse workspace:

1)Slow Workspace Load Time: The Synapse workspace has been taking significantly longer to load than expected. This delay is impacting our workflow and productivity.

2)Long Publishing Time to Master Branch: When publishing changes to the master branch, it takes an unusually long time to complete the process. This has been causing delays in our deployment and release cycles.

Could you please assist us in investigating and resolving these issues? Your support would be greatly appreciated.

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
5,200 questions
0 comments No comments
{count} votes

Accepted answer
  1. Vinodh247 28,371 Reputation points MVP
    2025-02-20T14:24:47.1866667+00:00

    Hi ,

    Thanks for reaching out to Microsoft Q&A.

    Performance issues like slow workspace loading and long publishing times in synapse can arise due to several factors. Here are some potential causes and steps to troubleshoot and resolve them:

    1. Slow Synapse Workspace Load Time

    Possible Causes & Fixes:

    • Browser Cache Issues: Clear your browser cache and try using an incognito window.
    • Too Many Artifacts (Pipelines, Notebooks, Datasets, etc.): Large numbers of resources can slow down workspace loading. Consider organizing or archiving unused artifacts.
    • Network Latency: Test your network connection speed and consider using a VPN if accessing Synapse from a remote location.
    • Azure Region Performance: If your Synapse workspace is in a region experiencing high demand, performance might degrade. Check Azure Service Health in the Azure Portal.
    • Integration with External Services: Linked services or external dependencies (like Data Lake, SQL Pools, or third-party connectors) can slow down loading if they experience issues.

    Troubleshooting Steps:

    1. Check Azure Service Health (Azure Status Page) for ongoing issues.
    2. Test in Different Browsers or Machines to rule out local issues.
    3. Disable Unused Extensions in Browser (ad blockers, VPNs, etc.).
    4. Check Azure Resource Utilization Metrics in Azure Monitor.
    1. Long Publishing Time to Master Branch

    Possible Causes & Fixes:

    • Large Number of Changes: If there are too many changes in Synapse artifacts, publishing may take longer.
    • Git Integration Performance Issues: Slow sync with the remote repository can cause delays.
    • Workspace Metadata Size Growth: Synapse stores metadata for linked services, datasets, and pipelines, which may grow over time and slow down publishing.
    • Long-Running Dependencies: If you have dependencies such as Spark pools or SQL pools, ensure they are properly optimized.

    Troubleshooting Steps:

    1. Optimize the Number of Changes – Commit and publish in smaller batches.
    2. Check Git Repository Performance – If using Azure DevOps or GitHub, check if the repository is slow.
    3. Monitor Synapse Logs - Use Synapse Studio --> Monitor --> Activity Runs for any errors.
    4. Reintegrate Git Repository – Disconnect and reconnect Git integration in Synapse Studio --> Manage --> Git Configuration.
    5. Check SQL/Spark Pool Health – Ensure SQL pools are paused when not in use and Spark pools are properly configured.

    Raise a support ticket with azure if nothing worked.

    Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.