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
Hi, I recently integrated some of tracy's Mutex instrumentation. It's very close to being perfect for my use case, however without support for RwLocks or Semaphores, it falls a bit short.
For an RwLock a half-measure is to only mark write locks, but this means tracy isn't aware of contention on acquiring read locks, which leads to unmarked contention. On the flip side, marking on both writes and reads will incorrectly give you the impression that your reads are contending with each other.
Points where my threads sleep on (unmarked) attempted RwLock read lock acquisitions:
Plotting a Semaphore's permits may help a little, but didn't provide me useful insight on my RwLocks.
I'd like to request these features if they have not already.
The text was updated successfully, but these errors were encountered:
Hi, I recently integrated some of tracy's Mutex instrumentation. It's very close to being perfect for my use case, however without support for RwLocks or Semaphores, it falls a bit short.
For an RwLock a half-measure is to only mark write locks, but this means tracy isn't aware of contention on acquiring read locks, which leads to unmarked contention. On the flip side, marking on both writes and reads will incorrectly give you the impression that your reads are contending with each other.
Points where my threads sleep on (unmarked) attempted RwLock read lock acquisitions:

Plotting a Semaphore's permits may help a little, but didn't provide me useful insight on my RwLocks.
I'd like to request these features if they have not already.
The text was updated successfully, but these errors were encountered: