cloudfoundry / cloudfoundry/stratos

Too much app make stratos lags

Open
#4,278 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community scalability
Dominant language
TypeScript
Stars
267
Forks
137
Avg merge
5h 14m
Merged PRs (30d)
77

Description

Detailed Description

Hello, I'm a developer in a big company and we have around 100 apps in each ORG.
When we connecting on Stratos, the front loads all apps with this call:

https://stratosurl/pp/v1/proxy/v2/apps?order-direction=asc&order-direction-field=creation&page=1&results-per-page=100&inline-relations-depth=2&include-relations=space,organization,routes

So we need to load around 5MB of data, and It's make the client freeze for a while.

Most part of time we don't need to load all cloud foundry ORGS

So we would like an option to prevent load of all ORG cause we always need to wait 2/3 minutes to have the entire Stratos loaded. So it's more quickly to use command line.

Possible Implementation

Have an option for each user to have a default ORG to avoid to load all datas.

I have already tried to code a plugin for chrome who replace the original url with:

https://stratosurl/pp/v1/proxy/v2/spaces/{myspaceid}/apps?order-direction=asc&order-direction-field=creation&page=1&results-per-page=100&inline-relations-depth=2&include-relations=space,organization,routes

It's more fast but it's hard coded. We would prefer to have an option on Stratos to do that.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Stratos frontend flow that requests the /pp/v1/proxy/v2/apps endpoint with results-per-page=100 and organization relations. Define how a per-user default organization should affect loading, then verify that the selected organization loads without fetching every organization’s apps and that the full app view remains available when needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
cloud, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.