Skip to content

Clarify Recommendation Mapping Logic (Traffic Profile & SLO Levels) #28

@toslali-ibm

Description

@toslali-ibm

It would be nice to have a clear documentation explaining how the specification mapping logic works—specifically how traffic profiles and SLO levels are interpreted and mapped.

  • What do the High / Medium / Low levels actually represent?
  • How are these levels translated into: expected request rates, concurrency, latency/SLO requirements, throughput assumptions?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions