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
ThreadSafeFury uses ThreadLocal to ensure thread safety, which causes it to create a Fury object for each thread, even if the thread type is VirtualThread. We know VirtualThread is designed as a lightweight thread with an extremely short lifecycle, where creation and destruction occur very frequently. However, the creation cost of Fury objects is very high. In this scenario, the current implementation of ThreadSafeFury will lead to significant resource consumption. Do you have any suggestions for addressing this issue?
The text was updated successfully, but these errors were encountered:
Question
ThreadSafeFury uses ThreadLocal to ensure thread safety, which causes it to create a Fury object for each thread, even if the thread type is VirtualThread. We know VirtualThread is designed as a lightweight thread with an extremely short lifecycle, where creation and destruction occur very frequently. However, the creation cost of Fury objects is very high. In this scenario, the current implementation of ThreadSafeFury will lead to significant resource consumption. Do you have any suggestions for addressing this issue?
The text was updated successfully, but these errors were encountered: