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
We have integrated the phoenix_pubsub into our application and it is great. I noticed in the Phoenix.Tracker.State module that that "values" ets table is created via the following command:
values: :ets.new(:values, [:ordered_set])
When one calls the Phoenix.Tracker.list function it is returning a copy of the State object and it then calls an :ets.select on :values tid. Since this query is happening on a caller process and not the GenServer managing the state object, I was wondered why {read_concurrency, true} is not given as an option?
For our use cases when a user logins in they pull a friends list and check it against the Tracker system so we are doing a lot of current reads.
Thanks!
The text was updated successfully, but these errors were encountered:
Hey all,
We have integrated the phoenix_pubsub into our application and it is great. I noticed in the Phoenix.Tracker.State module that that "values" ets table is created via the following command:
When one calls the
Phoenix.Tracker.list
function it is returning a copy of the State object and it then calls an:ets.select
on :values tid. Since this query is happening on a caller process and not the GenServer managing the state object, I was wondered why{read_concurrency, true}
is not given as an option?For our use cases when a user logins in they pull a friends list and check it against the Tracker system so we are doing a lot of current reads.
Thanks!
The text was updated successfully, but these errors were encountered: