Oran Agra c4fdf09c05 prevent client tracking from causing feedback loop in performEvictions (#8100) ... When client tracking is enabled signalModifiedKey can increase memory usage, this can cause the loop in performEvictions to keep running since it was measuring the memory usage impact of signalModifiedKey. The section that measures the memory impact of the eviction should be just on dbDelete, excluding keyspace notification, client tracking, and propagation to AOF and replicas. This resolves part of the problem described in #8069 p.s. fix took 1 minute, test took about 3 hours to write.		2020-12-06 14:51:22 +02:00
..
assets	Tests: Add aclfile load and save tests (#7765)	2020-09-09 17:13:35 +03:00
cluster	Backup keys to slots map and restore when fail to sync if diskless-load type is swapdb in cluster mode (#8108)	2020-12-02 13:56:11 +02:00
helpers	revert an accidental test code change done as part of the tls project	2019-12-01 16:10:09 +02:00
integration	Modify help msg PING_BULK to PING_MBULK in benchmark (#8109)	2020-12-02 13:17:25 +02:00
modules	Make sure we do not propagate nested MULTI/EXEC (#8097)	2020-12-06 13:14:18 +02:00
sentinel	Recalculate hardcoded variables from $::instances_count in sentinel tests (#7561)	2020-09-13 18:39:59 +03:00
support	Extend client tracking tests (#7998)	2020-11-09 22:54:47 +02:00
tmp	minor fixes to the new test suite, html doc updated	2010-05-14 18:48:33 +02:00
unit	prevent client tracking from causing feedback loop in performEvictions (#8100)	2020-12-06 14:51:22 +02:00
instances.tcl	Allow blocked XREAD on a cluster replica (#7881)	2020-10-06 21:43:30 +03:00
test_helper.tcl	Tests: fix filename reported in run_solo tests.	2020-11-04 21:43:55 +02:00