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

Best practice for running with a persistent storage backend in AWS #221

Open
nikhilo opened this issue Apr 28, 2023 · 2 comments
Open

Best practice for running with a persistent storage backend in AWS #221

nikhilo opened this issue Apr 28, 2023 · 2 comments
Labels
waiting for answer Waiting for user's answer

Comments

@nikhilo
Copy link

nikhilo commented Apr 28, 2023

I have been trying to set this up in AWS ECS Fargate with EFS as the storage backend. Unfortunately the report generation takes a very long time, as compared to the same service running on ECS Fargate with ephemeral storage backend.
Any suggestion on the best way to set this up with persistent storage on AWS ?

@dineshmcac I noticed in #219 that you are using EFS as the storage backend. Are you able to get reasonable performance with EFS ? If yes, would you be able to share how you have set this up?

@dineshmcac
Copy link

Sorry @nikhilo I am not from devops/cloud team , I am just using the generated template. When it comes to performance I dont see any issues

@fescobar
Copy link
Owner

Hi @nikhilo
Make sure you use CHECK_RESULTS_EVERY_SECONDS=NONE and clean the results using the API
Please, check the note in the doc https://github.com/fescobar/allure-docker-service?tab=readme-ov-file#MULTIPLE-PROJECTS---REMOTE-REPORTS

@fescobar fescobar added the waiting for answer Waiting for user's answer label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for answer Waiting for user's answer
Projects
None yet
Development

No branches or pull requests

3 participants