erlang ets heir read_concurrency

最新推荐文章于 2021-08-28 23:00:07 发布

Anasterian

最新推荐文章于 2021-08-28 23:00:07 发布

阅读量1.2k

点赞数

分类专栏： erlang 文章标签： erlang

本文链接：https://blog.csdn.net/taitoubiyan1/article/details/41482957

版权

erlang 专栏收录该内容

33 篇文章 1 订阅

订阅专栏

ets 在创建的时候有这个一个选项 read_concurrency

官方文档解释如下

{read_concurrency,boolean()} Performance tuning. 
Default is false. When set to true, the table is optimized for concurrent read operations. 
When this option is enabled on a runtime system with SMP support, read operations become much cheaper; 
especially on systems with multiple physical processors.However, switching between read and write operations becomes more expensive. 

You typically want to enable this option when concurrent read operations are much more frequent than write operations, or when concurrent 
reads and writes comes in large read and write bursts (i.e., lots of reads not interrupted by writes,and lots of writes not interrupted by reads). 
You typically do not want to enable this option when the common access pattern is a few read operations interleaved with a few write operations repeatedly. 
In this case you will get a performance degradation by enabling this option. The read_concurrency option can be combined with the write_concurrency option. 
You typically want to combine these when large concurrent read bursts and large concurrent write bursts are common.

大致意思是，开启这个属性后并发读效率提升，但是读/写之间切换效率会降低。

当有连续读需求，并且中间不穿插写操作时，可以试一下开启这个功能

做了一个小测试

%%首先启动三个ets log_time用于记录每个查询操作消耗的时间
ets:new(open_concurrency, [set, public, named_table, {keypos, 1}, {read_concurrency,true}].
ets:new(close_concurrency, [set, public, named_table, {keypos, 1}, {read_concurrency,false}].
ets:new(log_time, [set, public, named_table, {keypos, 1}, {read_concurrency,true}].

read(EtsName) ->
    %%选择一个ets表先写入数据用于被查询
    FunUpdate = 
              fun(Nth) ->
                       cache:update(EtsName, Nth, Nth)
              end,
    lists:foreach(FunUpdate, lists:sql(1, 10000)),
    ets:delete_all_objects(log_time),

    FunGetTime = 
               fun(Nth) -> 
                   spawn(fun() ->
                         SelectNth = utils:rand(1, 10000),
                        {SelectTime, _} = timer:tc(fun() ->
                                          cache:get_value(EtsName, SelectNth)
                                                   end),
                         %%由于在子进程内，只能将时间数据储存在ets中
                         cache:update(log_time, Nth, SelectTime)
                         end)
                end,
    lists:froeach(FunPrint, lists:seq(1, 1000000)).
    %%随后再从log_time中将时间相加

对开启并发读/不开启并发读的ets分别做了100万次的读取,

在windows上测试了下结果，发现不开启并发读的时间竟然每次都少。。。

有时间了再去linux环境下看看。。