summaryrefslogtreecommitdiff
path: root/source4/torture/raw/lockbench.c
AgeCommit message (Collapse)AuthorFilesLines
2007-10-10r23182: fixed valgrind errorAndrew Tridgell1-0/+2
(This used to be commit fae416cbe8e44bc88ea709160a583e2f921e4eec)
2007-10-10r23181: prevent attempts to reopen the connection twice at the same timeAndrew Tridgell1-9/+13
(This used to be commit a25c27dbae4534f2125001c16ac9ae0b67c519cb)
2007-10-10r23180: auto-reconnect on both NT_STATUS_END_OF_FILE and ↵Andrew Tridgell1-2/+4
NT_STATUS_LOCAL_DISCONNECT (This used to be commit 32a6c268a7963382dc05f53783ac22f7fd0de429)
2007-10-10r23143: error found by valgrindAndrew Tridgell1-4/+5
(This used to be commit 268a26131ee43a673e7b79a359b2575dcef554d5)
2007-10-10r23142: added error checking and reconnect on echo repliesAndrew Tridgell1-4/+25
(This used to be commit 0d47efe6d6d1738183c59942a077faaf1c77f004)
2007-10-10r23140: send send echos while disconnectedAndrew Tridgell1-1/+3
(This used to be commit 233172a9f71e297e255c393946ad51fad96b356e)
2007-10-10r23139: use echo operations once a second in lockbench and openbench to ensureAndrew Tridgell1-0/+10
we detect IP takeover on servers (This used to be commit b5292a25edf1c071dea19877fb6b31f2501132ef)
2007-10-10r22965: changed RAW-LOCK-BENCH to remove the scheduling uncertainty. We shouldAndrew Tridgell1-52/+60
always get balanced locking now (This used to be commit 4e6df7b9b1938b91a904ab061c36d65b169f93a8)
2007-10-10r22962: show progress separately for each client in RAW-BENCH-LOCK, this isAndrew Tridgell1-15/+26
much more useful for seeing why we get unbalanced locking (This used to be commit 1f1f57023b6d7d7d4938803e57f30e485ccba719)
2007-10-10r22881: show number of connected clientsAndrew Tridgell1-2/+12
(This used to be commit 42f6c5106ea4d0e35f88e0c9523cbd13206fecb5)
2007-10-10r22876: - try to reconnect once per second, not continouslyAndrew Tridgell1-6/+12
- patch from ronnie to fix the lock offset on reconnect (This used to be commit 77d7ca5590bfc416a2526bc8833158df4e9d7810)
2007-10-10r22837: make RAW-BENCH-LOCK reconnect asynchronously when one of its serversAndrew Tridgell1-28/+110
goges away (This used to be commit cf0cdf5171d4e0ca01b697155ceb04ffc2863231)
2007-10-10r22836: started adding auto-reconnect logic to lockbench. This needs to beAndrew Tridgell1-2/+37
made async. (This used to be commit 9e1ea3e09c80adb0b9809ee83e0c7b1ec9156e42)
2007-10-10r22579: disable progress printing in the build-farmStefan Metzmacher1-2/+5
metze (This used to be commit 93089ad5e8b6e20c4fa92bf13b0137765aeac689)
2007-10-10r21216: fail the RAW-BENCH-LOCK test if the locking doesn't happen evenlyAndrew Tridgell1-1/+10
across the connections (This used to be commit 01ef699981f3bcbbbdd4a47d9b85324aec783451)
2007-10-10r20886: fixed a valgrind errorAndrew Tridgell1-0/+1
(This used to be commit acc96e42e74005f1c381b0ab3f6c1b2e051ffaec)
2007-10-10r20092: added a locking benchmark that should be good for benchmarkingAndrew Tridgell1-0/+196
communitcation in a CIFS clustered server. It tries to keep the connections full by setting up the next lock as each lock is done. The locking pattern is similar to the local filesystem ping pong test in junkcode, forcing a communication between nodes on each request (This used to be commit d57b9fb29860bd03cfa970bcc52ef45d17775638)