Forum Discussion

BalfourBen's avatar
BalfourBen
Advocate I
1 year ago
Solved

Can Too Many Workspace Cause issues

Hi All,

 

We are currently trying to establish a strategy for our workspace creations and we are aiming for departmental workspaces however some are looking for more granular level of workspaces.

 

After doing some research I have come across the below statement and I am trying to understand if anyone has come across this as an issue?

 

'Granular workspaces compete for limited memory and CPU, causing slower performance and refresh failures.'

  • BalfourBen's avatar
    BalfourBen
    1 year ago

    shashiPaul1570_  Thank you for this, My primary concern is manageability with a team of only 2 managing a large scale network of workspaces inclusive of security etc, some of which will likely end up with duplicated reports across workspaces. 

     

    Managing that sort of infrastructure feels difficult with the team size. The Performance cost on the Capacity would have potentially helped my decision.

     

    Thank you for your Help!

3 Replies

  • shashiPaul1570_'s avatar
    shashiPaul1570_
    Responsive Resident

    Hi BalfourBen,

    The number of workspaces alone doesnโ€™t cause slowdowns. All workspaces assigned to the same capacity share the same pool of memory and CPU. Performance issues arise if many heavy workloads run in parallel and compete for those shared resources.

    ๐Ÿ‘‰ Best practices:

    • Use the Capacity Metrics App to monitor usage.

    • Stagger refresh schedules to avoid concurrency spikes.

    • Scale up/out capacity if workload consistently exceeds limits.

    • Let governance and security drive workspace granularity, not performance fears.

    So yes, granular workspaces can add to the workload picture, but they donโ€™t slow things down by themselves โ€” itโ€™s the cumulative activity across the capacity that matters.

     

    Hope this clarifies ๐Ÿ™Œ. If helpful, please give a Kudos ๐Ÿ‘ and mark as Accepted Solution โœ… so others can benefit.

     

     

    Thanks 
    Shashi Paul 

    • BalfourBen's avatar
      BalfourBen
      Advocate I

      shashiPaul1570_  Thank you for this, My primary concern is manageability with a team of only 2 managing a large scale network of workspaces inclusive of security etc, some of which will likely end up with duplicated reports across workspaces. 

       

      Managing that sort of infrastructure feels difficult with the team size. The Performance cost on the Capacity would have potentially helped my decision.

       

      Thank you for your Help!

      • shashiPaul1570_'s avatar
        shashiPaul1570_
        Responsive Resident

        Hi BalfourBen,

        That makes sense โ€” with a small admin team, the bigger challenge is governance and manageability rather than capacity performance. A few best practices to consider:

        • Use fewer, departmental workspaces instead of many granular ones. This reduces overhead and keeps security easier to manage.

        • Rely on shared/certified datasets so reports can connect to a single trusted source, avoiding duplication across workspaces.

        • Leverage the Admin Monitoring workspace and Capacity Metrics App for visibility, and use REST APIs/PowerShell to automate repetitive admin tasks.

        This approach balances control with manageability and should keep things practical for a small team.

        Hope this helps ๐Ÿ™Œ If it does, please drop a Kudos ๐Ÿ‘ and mark it as Accepted Solution โœ… so others can benefit.

        Best regards,
        Shashi Paul