Has anyone experimented with the “Automatically use optimal number of data readers”?
I set this on some test SubClients and it is defaulting to 1 regardless of what the manual setting is. This results in jobs taking dramatically longer?
Does anyone know how the readers are optimised?
Why does it default to 1 regardless of the starting position?
Best answer by MarkP
Thanks, yes I had understood that part, I think the confusion arises because it is there as an option on Subclients that don’t support this technique. You have to delve in the documentation to find the references.
I would suggest that the dialogue is updated to reflect the use case properly and the online documentation specifically references that the option is not valid for standard Subclients.
Applies to: Windows file system agent, UNIX file system agent, Laptop agent, and multi-node agents such as Network Shares, Hadoop, GPFS, GlusterFS, and LustreFS.
When you select this option, the software automatically assigns the number of streams or readers required to perform the backup operations. The number of data readers that are assigned are based on the number of nodes configured for the subclient. This option is enabled by default.
Can you confirm how many nodes you have configured for the subclient? I’m wondering if it is working as expected, but because you only have 1 node (and therefore, that’s the best number to use).
Reading the documentation and looking at my configuration the “nodes” statement makes no sense.
Where is this configured? The only place I can see is the Lustre Pseudo client where clearly there are Data Access Nodes so if it applies to this I can see some logic.
At the moment it appears that a new default configuration is effectively halving the performance. On a Applying it by default to everything appears counter-intuitive and I struggle to see the benefit, particularly when the default is 1 compared to 2 previously.
Could you select the “Allow multiple data readers within a drive or mount point” option checked under the advanced sub-client properties under the performance tab
Thanks, yes I had understood that part, I think the confusion arises because it is there as an option on Subclients that don’t support this technique. You have to delve in the documentation to find the references.
I would suggest that the dialogue is updated to reflect the use case properly and the online documentation specifically references that the option is not valid for standard Subclients.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.