Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

Large enterprise customers are experiencing significant performance degradation in Red Hat Developer Hub (RHDH) as their Software Catalog scales. These issues manifest as long load times, frequent pod restarts (OOMKilled), and database crashes. 

This feature focuses on refining our performance and scaling tests to more closely match customer environments and workflows to help us get an accurate baseline and assess where the highest priority changes should be targeted to improve the customer experience at scale. 

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

• Update the performance testing environment and test suite to align with some of our larger customers 
• Cover key customer usage patterns - scaffolder, orchestrator, homepage, catalog, etc
• Investigate the results and create a followup plan we can drive into further features and improvements. E.g.
  • Incorrect instance sizing
  • Anti pattern in code
  • Missing database index
  • Database architecture
  • Specific slow plugins
  • Network issue
  • Connection pooling
  • Not using cache properly

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

• Performance tests must more closely match the load of large production environments
  • Environments need to remain performant and reliable with 30,000+ developers, 500,000+ groups, and 70,000 catalog applications 
  • Orchestrator instance should be able to run 50,000 daily workflows on the RHDH instance

Out of Scope (Optional)

High-level list of items that are out of scope.

Engineering work to improve performance will be handled in additional features 

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

<your text here>