{L_BUTTON_AT}Scrums
So that we can better understand your problem.
Thanks titanrx8 but this doesn't really solve my problem. I want to continue to use BTRFS. I am currently searching through the TOS scripts to see if I can find more information about this process.titanrx8 wrote: ↑28 May 2021, 22:55 When I set up my new F2-221, I switched to EXT4 with no snapshots instead of BTRFS with snapshots. I haven't seen TNASDBD take over the CPU since then. I also changed my PC backups to incremental file backup on the NAS so I'm not depending on the NAS to maintain the incrementals. Of course this means that I have no incrementals for files stored only on the NAS so I backup the NAS more often.
Okay I have narrowed this down to Redis server. Not exactly rocket science as the line above in services is redis_server. I'm struggling to see why I need this. Can it be removed or disabled? I use Emby and as far as I can see it doesn't depend on Redis. I would like to try disabling it. Can anyone tell me how to do this?Scrums wrote: ↑30 May 2021, 18:42Thanks titanrx8 but this doesn't really solve my problem. I want to continue to use BTRFS. I am currently searching through the TOS scripts to see if I can find more information about this process.titanrx8 wrote: ↑28 May 2021, 22:55 When I set up my new F2-221, I switched to EXT4 with no snapshots instead of BTRFS with snapshots. I haven't seen TNASDBD take over the CPU since then. I also changed my PC backups to incremental file backup on the NAS so I'm not depending on the NAS to maintain the incrementals. Of course this means that I have no incrementals for files stored only on the NAS so I backup the NAS more often.
I assume Redis server is needed as I tried shutting down the Redis server and was no longer able to log on to TOS or SSH though I was still able to access folders and files.. Out of interest I ran: # redis-cli 127.0.0.1:6379> DBSIZE (integer) 113 That means that the TNASDBD database only has 113 keys. So why on earth does it use so much CPU to reindex?????Scrums wrote: ↑30 May 2021, 22:43Okay I have narrowed this down to Redis server. Not exactly rocket science as the line above in services is redis_server. I'm struggling to see why I need this. Can it be removed or disabled? I use Emby and as far as I can see it doesn't depend on Redis. I would like to try disabling it. Can anyone tell me how to do this?Scrums wrote: ↑30 May 2021, 18:42Thanks titanrx8 but this doesn't really solve my problem. I want to continue to use BTRFS. I am currently searching through the TOS scripts to see if I can find more information about this process.titanrx8 wrote: ↑28 May 2021, 22:55 When I set up my new F2-221, I switched to EXT4 with no snapshots instead of BTRFS with snapshots. I haven't seen TNASDBD take over the CPU since then. I also changed my PC backups to incremental file backup on the NAS so I'm not depending on the NAS to maintain the incrementals. Of course this means that I have no incrementals for files stored only on the NAS so I backup the NAS more often.
1. Is Redis indexing all my data? That I do not know yet…Scrums wrote: ↑31 May 2021, 00:00I assume Redis server is needed as I tried shutting down the Redis server and was no longer able to log on to TOS or SSH though I was still able to access folders and files..Scrums wrote: ↑30 May 2021, 22:43Okay I have narrowed this down to Redis server. Not exactly rocket science as the line above in services is redis_server. I'm struggling to see why I need this. Can it be removed or disabled? I use Emby and as far as I can see it doesn't depend on Redis. I would like to try disabling it. Can anyone tell me how to do this?
Out of interest I ran:
# redis-cli
127.0.0.1:6379> DBSIZE
(integer) 113
That means that the TNASDBD database only has 113 keys. So why on earth does it use so much CPU to reindex?????
I downloaded a trial of an Excel connector add-in and could see that the Redis Is only recording system events such as high disc temperature. From TOS I cleared all notifications. There are now only four keys in the database. I will keep monitoring to see if this grows over time and has any effect on CPU usage for TNASDBD.Scrums wrote: ↑31 May 2021, 14:581. Is Redis indexing all my data? That I do not know yet…Scrums wrote: ↑31 May 2021, 00:00I assume Redis server is needed as I tried shutting down the Redis server and was no longer able to log on to TOS or SSH though I was still able to access folders and files..Scrums wrote: ↑30 May 2021, 22:43
Okay I have narrowed this down to Redis server. Not exactly rocket science as the line above in services is redis_server. I'm struggling to see why I need this. Can it be removed or disabled? I use Emby and as far as I can see it doesn't depend on Redis. I would like to try disabling it. Can anyone tell me how to do this?
Out of interest I ran:
# redis-cli
127.0.0.1:6379> DBSIZE
(integer) 113
That means that the TNASDBD database only has 113 keys. So why on earth does it use so much CPU to reindex?????
2. I don't think there is any way (that I can see anyway) to exclude folders from Redis
3. Looking at the Redis.conf I can see that compression is turned on:
# Compress string objects using LZF when dump .rdb databases?
# For default that's set to 'yes' as it's almost always a win.
# If you want to save some CPU in the saving child set it to 'no' but
# the dataset will likely be bigger if you have compressible values or keys.
rdbcompression yes
If Redis is just storing TOS configuration surely compression is not needed?