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

Create a specific HOT Exports for training #92

Open
severinmenard opened this issue Mar 4, 2015 · 2 comments
Open

Create a specific HOT Exports for training #92

severinmenard opened this issue Mar 4, 2015 · 2 comments

Comments

@severinmenard
Copy link

From the beginning, a large majority of the jobs come from training sessions. Considering these jobs are not for long term and the server is often overloaded, it would be better to have a specific instance for training, with eg a weekly flush

@mataharimhairi
Copy link
Collaborator

Perhaps this is where the different level of users for the tool can come into play. With those of higher/trainer level can export larger areas but also have their data flushed on a regular basis

@severinmenard
Copy link
Author

This is a technical point I let techy people decide, whether if it better
to have separate instances for non/important tasks vs the ones that need to
work during crisis response. For the TM I heard that some techy people were
suggesting to have a specific instance for the crisis response, but the
contraints may be different between the two services.

Otherwise, having the possibility to testing on the TM dev instance is
really handy for TM project managers

On Wed, Jun 17, 2015 at 4:27 AM, mataharimhairi [email protected]
wrote:

Perhaps this is where the different level of users for the tool can come
into play. With those of higher/trainer level can export larger areas but
also have their data flushed on a regular basis


Reply to this email directly or view it on GitHub
#92 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants