Hi,
While I am going to fix the endpoint enhancement PR for tool, we started using the tool with our patches in pre-prod environments and as per the logs it tooks the below times for backing up whisper file from one of our graphite nodes
2018-08-16-16:20:04;INFO;Starting backup of 142910 whisper files
2018-08-16-22:26:58;INFO;Backup complete
So approximately 6hrs in pre-prod and our prod environments are much bigger.
Cronjob uses these params
/usr/local/bin/whisper-backup --bucket $(name_ --prefix /data/graphite/whisper --endpoint $(endpoint) --processes 8 --quiet backup s3
In your experience how many processes you think the tool can use for backups and are there any more configurable options to make backups faster. I was going to do a tar of the same backup dir to have comparison but I believe tar is going to be cpu-intensive. Is it safer to have more processes to make it faster. If you like to know about our hardware please let me know
Hi,
While I am going to fix the endpoint enhancement PR for tool, we started using the tool with our patches in pre-prod environments and as per the logs it tooks the below times for backing up whisper file from one of our graphite nodes
2018-08-16-16:20:04;INFO;Starting backup of 142910 whisper files
2018-08-16-22:26:58;INFO;Backup complete
So approximately 6hrs in pre-prod and our prod environments are much bigger.$(name_ --prefix /data/graphite/whisper --endpoint $ (endpoint) --processes 8 --quiet backup s3
Cronjob uses these params
/usr/local/bin/whisper-backup --bucket
In your experience how many processes you think the tool can use for backups and are there any more configurable options to make backups faster. I was going to do a tar of the same backup dir to have comparison but I believe tar is going to be cpu-intensive. Is it safer to have more processes to make it faster. If you like to know about our hardware please let me know