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

Performance tests - concurrent requests response time (Test80) #18

Open
2 tasks
nir-r opened this issue Jun 5, 2024 · 0 comments
Open
2 tasks

Performance tests - concurrent requests response time (Test80) #18

nir-r opened this issue Jun 5, 2024 · 0 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@nir-r
Copy link
Collaborator

nir-r commented Jun 5, 2024

Background

Article 3.5 in "Technical Guidelines and Requirements ‎Document for FHIR Infrastructure ‎Implementation"
https://www.fhir-il-community.org/%D7%A1%D7%A8%D7%98%D7%99%D7%A4%D7%99%D7%A7%D7%A6%D7%99%D7%94

‎3.5. Performance and availability requirements
Organizational FHIR platform SHALL maintain a minimum annual uptime of 99.95%.‎
Organizational FHIR platform SHALL meet the following performance targets for 100 ‎concurrent FHIR REST API requests:‎
‎-‎ ‎95th percentile of FHIR REST API responses SHALL be returned within 200 milliseconds.‎
‎-‎ ‎99th percentile of FHIR REST API responses SHALL be returned within 2000 ‎milliseconds.‎
Note that these requirements only define the criteria for the FHIR platform's uptime, response ‎times, and concurrency. Data latency requirements (i.e. - time between data updates in the ‎source system and their availability via FHIR REST API) are defined in the [B.3] Information ‎Requirements document.‎

Requirment

  • Integrate performance testing capabilities into FUME - use loadtest
  • Test loadtest client's ability to output the desired amount of requests - Expose an API in FUME to mimic a server that returns 200 OK on each response
@nir-r nir-r added the help wanted Extra attention is needed label Jun 5, 2024
@nir-r nir-r closed this as completed Jun 5, 2024
@nir-r nir-r reopened this Jun 5, 2024
@nir-r nir-r self-assigned this Jun 5, 2024
@nir-r nir-r moved this to Backlog in Certificator MVP Jun 6, 2024
@nir-r nir-r moved this from Backlog to Ready in Certificator MVP Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant