August 20, 2025Aug 20 Hello,I ran mover today cause one of my cache drive was getting full and was stunned to wait 1 hours before it reach that particular cache to move. I remember when looking at the log in the past that mover move 1 file at a time. I can understand why when we had a single cache and single parity pool. But now that we have multiple pool and cache, I though it would be nice to have parallel mover thread running.Easy way to do it would be to have a pool lock map. For exemple, in my system, I have:ArrayCacheAppData CacheDownloaddownload cacheCache move to array, array move to appdatacache (move appdata) and download cache move to cache.In that scenario, a simple lock table of 5 elements could be used, one for each pool. The first thread would be the cache to array which would lock cache and array pool. While lock, no thread can run on the locked one. So appdatacache won't run until array is unlock. But then, download cache to download can be run since it's using 2 unlocked pool.Thus, there would be 2 mover running while 1 job pending.I'm unsure if what I'm saying make sense or not, but that would greatly increase mover speed in a multi-pool scenario like mine.Thank you!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.