Results depend on Tracing API

[kingjunsung]

The simulation results vary depending on whether functions such as 'tracing.TraceReqReceive' in api.go are used.
Is there a way to make the simulation deterministic regardless of whether tracing is enabled?

[syifan]

Could you please let us know how to recreate this problem? In the current version, can I comment out a few tracing.TraceReqReceive so that the results are significantly different? In theory, they should not matter as they are read only.

[kingjunsung]

I implemented a custom GMMU, and I want to measure the average latency of each request. To do that, I placed multiple measurement points to put tracing API. However, every time I change the location of tracing API, the number of GMMU hits and misses changes.
I haven't tried it with the latest version, I'm currently using v3. But since you said it works well in the current version, I'll give that a try. Thanks!

[syifan]

I am not 100% sure that it works well in the current version. In theory, it should. But there may be some bugs. Could you try to play around the current tracing instrumentation and see if the results can change?

BTW, if you want deterministic results, use serial mode rather than parallel mode.