Commit Graph

34 Commits

Author SHA1 Message Date
sfc-gh-tclinkenbeard 4669f837fa Add uses of makeReference 2020-11-07 22:10:18 -08:00
sfc-gh-tclinkenbeard 012886a8d8 Fix Windows CMake build 2020-10-07 12:30:19 -07:00
sfc-gh-tclinkenbeard 7f0d14c8e4 Modernize/refactor workloads directory 2020-10-04 22:29:07 -07:00
Andrew Noyes bc412f39a6 Augment ReportConflictingKeys test to catch memory error 2020-07-24 23:31:00 +00:00
Chaoguang Lin a03a3c297d Add more detailed traces 2020-05-21 14:48:35 -07:00
Chaoguang Lin 8ab792d58b Add assertions that results are empty if no conflicts happen 2020-05-15 16:34:43 -07:00
Chaoguang Lin a65f767997 Using coinflip() to simplify the code 2020-05-15 16:34:43 -07:00
chaoguang c6a09559ee Allow multiple clients in report-conflicting-keys correctness test 2020-05-15 16:34:42 -07:00
chaoguang 2a6de93b92 add copyright information 2020-04-08 14:50:55 -07:00
chaoguang 20b2984841 fix issues according to andrew's comments 2020-04-08 12:43:25 -07:00
chaoguang a93c0053ca add two asserts 2020-04-03 19:09:12 -07:00
chaoguang 62627dd2ee Fix a randomness bug and naming issue in TraceEvent 2020-03-25 00:55:40 -07:00
Andrew Noyes 289487559d Revert "Revert "Merge pull request #2257 from zjuLcg/report-conflicting-key""
This reverts commit 804fe1b22e.
2020-03-24 18:11:15 -07:00
Balachandar Namasivayam 804fe1b22e Revert "Merge pull request #2257 from zjuLcg/report-conflicting-key"
This reverts commit 648dc4a933, reversing
changes made to 487d131b38.
2020-03-19 21:34:28 -07:00
chaoguang 9dc441c65a clang-format 2020-03-13 15:43:01 -07:00
chaoguang 39a37531db Fix issues according to Andrew's comments 2020-03-13 15:42:15 -07:00
chaoguang c246f79d72 Update comments 2020-03-13 13:18:18 -07:00
chaoguang a3b0dce3cd Rename vars, update comments 2020-03-13 13:12:22 -07:00
chaoguang 8ee4fea3d3 clang-format 2020-03-13 12:54:12 -07:00
chaoguang aef9b515de Change the workload to a more controlled test like ConflictRange test 2020-03-13 12:42:28 -07:00
chaoguang 7118759dfa Delete code to test resolvers' performance, simplify the workload to only test correctness 2020-03-13 01:48:55 -07:00
chaoguang 6f90228a0b change to krmSetRangeCoalescing 2020-03-12 11:31:36 -07:00
chaoguang c2f0c41c52 use krmSetRange 2020-03-11 23:12:38 -07:00
chaoguang 1a5b41157e add test for native transaction object 2020-03-11 11:17:34 -07:00
chaoguang 3a98c691b6 Update comments 2020-03-04 11:42:19 -08:00
chaoguang 5386b4ecdf Adding prefix to returned keys, keeping consistency with query range 2020-01-21 15:18:16 -08:00
chaoguang 72d39a31f1 Change to send back index of read_conflict_range not keys, which speeds up but fail to give narrowed keyrange 2020-01-15 10:21:51 -08:00
chaoguang 1cf3b5b807 Change to general prefix '\xff\xff/transaction/conflicting_keys/' 2020-01-13 20:54:16 -08:00
chaoguang 9a736dde8d delete wait in workload when checking, add assert to make sure the getRange for conflicting keys happens locally 2020-01-10 18:01:17 -08:00
chaoguang 57fb28af2c Explicitly set read-version and clear the whole keyspace to make sure the getRange happens locally 2020-01-07 13:54:33 -08:00
chaoguang 10719200c3 A hack way to call API through getRange("\xff\xff/conflicting_keys\<start_key>", "\xff\xff/conflicting_keys\<end_key>"). 2020-01-06 11:22:11 -08:00
chaoguang 9dc79488a8 narrow the returned conflicting ranges 2019-12-06 16:21:19 -08:00
chaoguang b376b947d5 Encode conflicting keys using base64. 2019-12-06 16:21:19 -08:00
chaoguang eacfdf6da3 Add a simple workload, ReportConflictingKeysWorkload, to test correctness of the API and performance overhead added to the resovler. 2019-12-06 16:21:03 -08:00