If the spawning process inherits the table won’t that make it the only process which can write to the table forcing a serialization point ?
I think you just got yourself a nice load testing project ![]()
At this point I’m not convince you are getting much gains over:
- Serializing all writes through one GenServer or
- Just making
etstable public and allowing the child processes to write directly to it
You make (2) a bit more protected by not naming the table and passing the Tid down to the child processes.






















