You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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).
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
The text was updated successfully, but these errors were encountered: