Dear sir/madam,
I would like to know the timing to reset the lpad.
How regularly and at what timing can we do the reset?
One possible timing would be when the mongodb server is temporary down for maintenance and all the calculations are already submitted. But, in the latter case, what should we do if the FIZZLED calculations remain?
Or, shouldn’t we reset the lpad at all?
Sincerely,
Yu
Hi Yu
Generally I would suggest not resetting the lpad at all. This would remove all your previously stored data, etc. and all accounting of your jobs.
If there are particular jobs that you no longer want to keep track of, I would suggest “archiving” those workflows (“lpad archive_wflows”):
https://materialsproject.github.io/fireworks/defuse_tutorial.html
If the entire database is not needed anymore, I would suggest backing up the database using the MongoDB backup operations (e.g., mongodump) and then removing it. But typically we keep our databases around unless it’s very clear the data is not needed anymore (e.g., testing purposes, and we have also deleted the calculation directories).
-Anubhav
On Tue, Nov 20, 2018 at 4:42 PM [email protected] wrote:
Dear sir/madam,
I would like to know the timing to reset the lpad.
How regularly and at what timing can we do the reset?
One possible timing would be when the mongodb server is temporary down for maintenance and all the calculations are already submitted. But, in the latter case, what should we do if the FIZZLED calculations remain?
Or, shouldn’t we reset the lpad at all?
Sincerely,
Yu
–
You received this message because you are subscribed to the Google Groups “atomate” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
–
Best,
Anubhav
Dear Anubhav,
Thank you very much for your prompt reply.
I was bit worried that if the number of stored data is very large, the lpad may be too heavy to run.
But I just worried for nothing.
Best wishes,
Yu
On Thursday, November 22, 2018 at 7:20:49 AM UTC+9, Anubhav Jain wrote:
Hi Yu
Generally I would suggest not resetting the lpad at all. This would remove all your previously stored data, etc. and all accounting of your jobs.
If there are particular jobs that you no longer want to keep track of, I would suggest “archiving” those workflows (“lpad archive_wflows”):
https://materialsproject.github.io/fireworks/defuse_tutorial.html
If the entire database is not needed anymore, I would suggest backing up the database using the MongoDB backup operations (e.g., mongodump) and then removing it. But typically we keep our databases around unless it’s very clear the data is not needed anymore (e.g., testing purposes, and we have also deleted the calculation directories).
-Anubhav
On Tue, Nov 20, 2018 at 4:42 PM [email protected] wrote:
Dear sir/madam,
I would like to know the timing to reset the lpad.
How regularly and at what timing can we do the reset?
One possible timing would be when the mongodb server is temporary down for maintenance and all the calculations are already submitted. But, in the latter case, what should we do if the FIZZLED calculations remain?
Or, shouldn’t we reset the lpad at all?
Sincerely,
Yu
–
You received this message because you are subscribed to the Google Groups “atomate” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
–
Best,
Anubhav
Hi Yu
MongoDB is meant to handle very large data sets, e.g. see:
https://www.mongodb.com/blog/post/processing-2-billion-documents-a-day-and-30tb-a
If you encounter performance issues in reality please let us know, I’m sure we can solve them.
Best,
Anubhav
Dear Anubhav,
Thank you very much for your kindness.
I keep trying fireworks/atomate. It’s really useful.
Best,
Yu
On Thursday, November 22, 2018 at 7:42:41 AM UTC+9, Anubhav Jain wrote:
Hi Yu
MongoDB is meant to handle very large data sets, e.g. see:
https://www.mongodb.com/blog/post/processing-2-billion-documents-a-day-and-30tb-a
If you encounter performance issues in reality please let us know, I’m sure we can solve them.
On Wed, Nov 21, 2018 at 4:40 PM [email protected] wrote:
Dear Anubhav,
Thank you very much for your prompt reply.
I was bit worried that if the number of stored data is very large, the lpad may be too heavy to run.
But I just worried for nothing.
Best wishes,
Yu
On Thursday, November 22, 2018 at 7:20:49 AM UTC+9, Anubhav Jain wrote:
Hi Yu
Generally I would suggest not resetting the lpad at all. This would remove all your previously stored data, etc. and all accounting of your jobs.
If there are particular jobs that you no longer want to keep track of, I would suggest “archiving” those workflows (“lpad archive_wflows”):
https://materialsproject.github.io/fireworks/defuse_tutorial.html
If the entire database is not needed anymore, I would suggest backing up the database using the MongoDB backup operations (e.g., mongodump) and then removing it. But typically we keep our databases around unless it’s very clear the data is not needed anymore (e.g., testing purposes, and we have also deleted the calculation directories).
-Anubhav
On Tue, Nov 20, 2018 at 4:42 PM [email protected] wrote:
Dear sir/madam,
I would like to know the timing to reset the lpad.
How regularly and at what timing can we do the reset?
One possible timing would be when the mongodb server is temporary down for maintenance and all the calculations are already submitted. But, in the latter case, what should we do if the FIZZLED calculations remain?
Or, shouldn’t we reset the lpad at all?
Sincerely,
Yu
–
You received this message because you are subscribed to the Google Groups “atomate” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
–
Best,
Anubhav
–
You received this message because you are subscribed to the Google Groups “atomate” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
–
Best,
Anubhav