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
...so that adding new measurement items during the sampling phase won't actually trigger reallocation (in most cases).
The recommended looping pattern of IPROF_SYNC calls lets the first loop cycle "break new ground" and record how many measurements have been made, then (after the actual syncing), that std::swap(measurements, unfinished); could be extended with a preallocation step for the new measurements instance.
Evaluate if that unfinished vector, recreated on every call, could just be thread_local instead!
The text was updated successfully, but these errors were encountered:
...so that adding new
measurement
items during the sampling phase won't actually trigger reallocation (in most cases).The recommended looping pattern of
IPROF_SYNC
calls lets the first loop cycle "break new ground" and record how many measurements have been made, then (after the actual syncing), thatstd::swap(measurements, unfinished);
could be extended with a preallocation step for the newmeasurements
instance.Evaluate if that
unfinished
vector, recreated on every call, could just be thread_local instead!The text was updated successfully, but these errors were encountered: