google-deepmind/reverb

How to interpret warning on Table access with/without gRPC

balloch opened this issue · 2 comments

balloch commented

Hey y'all, I am running my own variation on the DreamerV3 code that uses Reverb for the replay buffer, and I noticed that we frequently get the following warning:

Sampler and server are owned by the same process (13181) so Table table is accessed directly without gRPC

The warning also appears in the default responses of the Tensorflow REINFORCE tutorial which uses Reverb: https://www.tensorflow.org/agents/tutorials/6_reinforce_tutorial

With some light digging, it doesn't seem like there is any discussion of this on the web. We aren't expecially concerned as our code is running, but we would like to fix this if possible. Are there any implications of gRPC not being used, such as slowdowns in efficiency? What is the typical protocol to modify my Reverb implementation to get rid of this warning?

acassirer commented

Hey,

This message is not a warning but simply an info statement letting you know that Reverb was able to use a more efficient sample path (i.e. without using gRPC).

  • 👍1
thomasbbrunner commented

Is there a way to force reverb to use this local mode? I.e., force it to not serialize the data.

  • 👍1