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
I've received some feedback on the locks_leader, so some people seem to be using that (and I'm thinking about moving gproc onto it). Other than that, I'm not aware of any production use of the locking mechanism.
sorry i didn't see the module :) thanks. Also I think I already asked, but what about using the code for local locks? Would it be overkill? I'm wondering of the cost of using 1 process to maintain the transaction instead of maintaining locally for example.
is the source code of the bench application used in your presentation [1] available? is there any usage in prod you're aware of btw?
[1] http://www.erlang-factory.com/static/upload/media/1402393233214750euc14wigerlocks.pdf
The text was updated successfully, but these errors were encountered: