Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scaling to 100+ sites for an organization #153

Open
bhasselbeck opened this issue Jun 23, 2014 · 2 comments
Open

Scaling to 100+ sites for an organization #153

bhasselbeck opened this issue Jun 23, 2014 · 2 comments
Labels

Comments

@bhasselbeck
Copy link

We have an organization that has a lot of sites with pantheon. Often, we need a CLI to each site (irregardless of their activity or age). However, we get timed out whenever we try to fetch aliases or download the aliases. What can we do to generate alias files better? Could we make that process into a batch job?

This problem will only get worse as we're adding new sites everyday. We're often demoing sites for BIG customers, and we don't have time to take our team members off of other sites and adding them to new sites before having to demo.

@joshkoenig
Copy link
Contributor

Hey Brian,

This is a good question. The first option would be to make sure that alias fetching and site listing is performant with that many organizations. We'll need to take a quick look at where the bottleneck is before determining how to proceed.

@joshkoenig joshkoenig changed the title If I'm on 100+ sites as a team member, pantheon-aliases times out... Scaling to 100+ sites for an organization Jun 23, 2014
@mikevanwinkle
Copy link
Contributor

Does this happen consistently or just every now and then. How long does it take to timeout? Are you able to download aliases in the dashboard?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants