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
ethercalc works great with redis except one thing: the backup happens every 15s ! so the cpu for redis is near 100% !
Here the logs docker-compose logs -f
ethercalcDB | 438:C 12 Jul 2023 16:46:50.498 * DB saved on disk
ethercalcDB | 438:C 12 Jul 2023 16:46:50.558 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 1 MB
ethercalcDB | 1:M 12 Jul 2023 16:46:50.667 * Background saving terminated with success
ethercalcDB | 1:M 12 Jul 2023 16:46:51.019 * Background saving started by pid 439
ethercalcDB | 439:C 12 Jul 2023 16:47:04.780 * DB saved on disk
ethercalcDB | 439:C 12 Jul 2023 16:47:04.847 * Fork CoW for RDB: current 3 MB, peak 3 MB, average 2 MB
ethercalcDB | 1:M 12 Jul 2023 16:47:04.950 * Background saving terminated with success
ethercalcDB | 1:M 12 Jul 2023 16:47:05.096 * Background saving started by pid 440
I tried to start redis-server with command: redis-server --appendonly yes --save 60 10000 with no succes. I tried to look for the redis.conf file but it appears nowhere.
I guess something somewhere bypass my --save 60 10000 parameter. but where ?
thank you for any advice ;)
regards,
fabrice.
The text was updated successfully, but these errors were encountered:
fab-kaz
changed the title
Not an issue: it's a question abour backup the redis DB
Not an issue: it's a question about backup the redis DB
Jul 12, 2023
Hello,
ethercalc works great with redis except one thing: the backup happens every 15s ! so the cpu for redis is near 100% !
Here the logs
docker-compose logs -f
I tried to start redis-server with
command: redis-server --appendonly yes --save 60 10000
with no succes. I tried to look for the redis.conf file but it appears nowhere.I guess something somewhere bypass my
--save 60 10000
parameter. but where ?thank you for any advice ;)
regards,
fabrice.
The text was updated successfully, but these errors were encountered: