Add failing test
Test fails as fetching repeated object is too slow. ```Head check took 124301 microseconds checking list of length 5000 Head check took 112286 microseconds checking list of length 5000 Head check took 1336512 microseconds checking list of length 5 2018-12-10T11:54:41.342 B0013 <0.2459.0> Long running task took 260788 microseconds with task of type pcl_head 2018-12-10T11:54:41.618 B0013 <0.2459.0> Long running task took 276508 microseconds with task of type pcl_head 2018-12-10T11:54:41.894 B0013 <0.2459.0> Long running task took 275225 microseconds with task of type pcl_head 2018-12-10T11:54:42.173 B0013 <0.2459.0> Long running task took 278836 microseconds with task of type pcl_head 2018-12-10T11:54:42.477 B0013 <0.2459.0> Long running task took 304524 microseconds with task of type pcl_head``` It taks twice as long to check for one repeated object as it does to check for 5K non-repeated objects
This commit is contained in:
parent
401228c84e
commit
e73f48a18b
2 changed files with 103 additions and 2 deletions
|
@ -2028,7 +2028,7 @@ addto_ledgercache({H, SQN, KeyChanges}, Cache) ->
|
|||
-> ledger_cache().
|
||||
%% @doc
|
||||
%% Add a set of changes associated witha single sequence number (journal
|
||||
%% update) to the ledger cache. This is used explicitly when laoding the
|
||||
%% update) to the ledger cache. This is used explicitly when loading the
|
||||
%% ledger from the Journal (i.e. at startup) - and in this case the ETS insert
|
||||
%% can be bypassed, as all changes will be flushed to the Penciller before the
|
||||
%% load is complete.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue