Optimizing Workspace load times

There's multiple ways to organize Issues in repositories to optimize workflows within ZenHub. The more repositories you have in a Workspace, the slightly longer load times you may experience. To help teams optimize organization of work, below is a table outlining the impact of number of repos in a Workspace on performance and load times.

Load times and number of connected repositories

To optimize for performance when loading Workspaces, below are guidelines and performance impact based on the number of connected repos you roughly have within your team's Workspace.

Number of connected Repos

Load times

Notes

6 or less repos

Fast

There should not be any impact on load times unless you have thousands of Issues and complex webs of data across Issues. If you're experiencing slow loading and have a small Workspace, please let us know!

6-12 repos

Moderate

When surpassing 6 repos, we encourage conversation around how work is being organized and why this Workspace is getting quite large. Is this based on where Issues currently live in relation to where work is happening, do you have project-based repositories and are combining multiple projects to a centralized workflow?

12 or more repos

Slow

The more connected repositories you have, the more connections and information we need to pull across your GitHub environment to render your Workspaces. This includes potentially a high volume of Issues, Epics, dependencies, and meta data.

Issue-only Repos

To optimize workflows for load times and focused pipeline structures we often see teams leverage Issue-only repos. This allows teams to break away from where code-lives as the defining factor for how Issues get created to organize tasks and projects.

Having a repository belong to more than one Workspace

To help with load time performance, we're mid-development on Workspace functionality to support having a repository live in more than one Workspace, as well as have multiple Workspaces on the same repository. This will help accommodate complex team structures and workflow to keep multi-repo Board merges small. Teams will be able to optimize load times by creating project or team-specific workflows using smaller Workspaces.