[erlang-questions] Design question -- a valid or foolhardy approach to ets update?
Tue Jul 14 17:25:01 CEST 2009
On Jul 14, 2009, at 10:28 AM, Ulf Wiger wrote:
> From the documentation of ets:new(...):
> Performance tuning. Default is false, which means that the table is
> optimized towards concurrent read access. An operation that mutates
> (writes to) the table will obtain exclusive access, blocking any
> concurrent access of the same table until finished. If set to true,
> the table is optimized towards concurrent write access. Different
> parts of the same table can be mutated (and read) by concurrent
> processes. This is achieve to some degree at the expense of single
> access and concurrent reader performance. Table typ ordered_set is
> not affected by this option in current implementation."
Good stuff, I wasn't aware of that.
More information about the erlang-questions