Add dynamic config to disable loading task queue user data

[dhiaayachi]

Task queue user data is now in the critical path and loaded for every task queue partition (only the root reads from the DB). At the time of writing only versioning data is stored in user data and until we're confident with the user data mechanism, we need the ability to disable it.

[dhiaayachi]

Thank you for reporting this issue. We understand that having task queue user data in the critical path can impact performance.

Currently, there's no way to directly disable user data loading for task queues. However, you can consider the following workaround:

• Use a custom workflow implementation: Instead of relying on the built-in task queue mechanisms, you can create your own workflow implementation that manages task queues and doesn't use user data.

We appreciate your feedback and will consider adding the ability to disable user data loading in the future.

[dhiaayachi]

Thank you for reporting this issue. We understand that the current design of the task queue user data loading can impact performance.

Currently, we do not have a feature to disable user data loading for task queues. However, we are actively working on improving the efficiency of this process and plan to implement a solution in the future.

In the meantime, you can try the following workarounds:

• Minimize the amount of data stored in the user data: Consider reducing the amount of data you store in the user data to minimize the impact on performance.
• Optimize your data access: Ensure you are efficiently accessing the user data within your tasks. You can investigate using caching or other optimization techniques to reduce database calls.

We will keep you updated on any progress made towards implementing a feature to disable user data loading.

If you have any other questions or concerns, please don't hesitate to ask.

[dhiaayachi]

Thank you for reporting this issue. We understand that having task queue user data in the critical path and loaded for every task queue partition can be problematic, especially until the user data mechanism is fully established.

We are currently working on a way to disable user data loading for task queues. In the meantime, you can work around this issue by:

• Removing unnecessary user data: If you are not actively using any user data, you can remove it from your task queues to reduce the impact on performance.
• Minimizing user data size: If you need to use user data, you can try to minimize its size to reduce the time it takes to load.

We are actively working on a solution to this issue and will update the documentation once it is available.

Please let us know if you have any further questions.