Open krishnapaparaju opened 6 years ago
500 components analysis (SLA: 1 sec) requests concurrently.
How is this defined? 1 sec for one component analysis?
@fridex Yes, OSIO user triggering component analysis would expect the response in 1 second and response for stack analysis in not more than 2 mins.
@fridex Yes, OSIO user triggering component analysis would expect the response in 1 second and response for stack analysis in not more than 2 mins.
Is it response from API server in both cases?
Yes
Yes
OK, thanks for clarification.
@samuzzal-choudhury @sivaavkd @GeorgeActon scaling the platform for significantly higher number of users is on the critical path for opening up the platform for IDE users.
Component analyses are OK-ish (not flawless though): https://github.com/openshiftio/openshift.io/issues/1243#issuecomment-342399807
There will be some work around stack analyses: https://github.com/openshiftio/openshift.io/issues/1242#issuecomment-342418630
Need to scale OSIO analytics to process 100 stack analysis requests (SLA: 2 mins) , 500 components analysis (SLA: 1 sec) requests concurrently.
This work is being tracked here and all the code/configuration changes that would be made to achieve the above goal around scalability.
https://docs.google.com/a/redhat.com/spreadsheets/d/13CRoYJPxGrDkhgnTKeyjP80SVdY0Sdfg6bbGlIT6azY/
cc @msrb @samuzzal-choudhury @msrb @GeorgeActon @sivaavkd
Sprint 144
Scale the platform to support 1000 concurrent users:
Stretch:
Sprint 143 User Story
Sprint 142 Checklist
Checkist:
Related issues: