8 Commits

Author SHA1 Message Date
antirez
271db42742 Fix test false positive introduced by threaded I/O.
Now clients that are ready to be terminated asynchronously are processed
more often in beforeSleep() instead of being processed in serverCron().
This means that the test will not be able to catch the moment the client
was terminated, also note that the 'omem' figure now changes in big
steps, because of the new client output buffers layout.

So we have to change the test range in order to accomodate for that.
Yet the test is useful enough to be worth taking, even if its precision
is reduced by this commit. Probably if we get more problems, a thing
that makes sense is just to check that the limit is < 200k. That's more
than enough actually.


Former-commit-id: 8aaa8b0b116dc86473b6a94bf2ff330dd4163ca1
2019-07-18 23:12:05 -04:00
John Sully
33f32477da We can use less memory in the client output buffers. Its OK
Former-commit-id: 852819180f6a281449a376b6b79a424af4e63c82
2019-07-05 23:43:01 -04:00
antirez
c4db57ceaf Test: obuf-limits test false positive removed.
Fixes #621.
2013-03-25 11:56:34 +01:00
antirez
758de4c3d6 even less false positive on obuf-limits test. 2012-02-22 11:25:30 +01:00
antirez
eeb8c0a5f5 minimal change to obuf-limits.tcl test to make sure there are no false positives with 32bit instances as well. 2012-01-30 21:08:10 +01:00
antirez
3638a60058 Less false positives for obuf-limits.tcl tests 2012-01-26 16:08:24 +01:00
antirez
e28a9ac80d Added test for client output buffer limit (soft limit). 2012-01-25 18:34:56 +01:00
antirez
fc001ea069 Added test for client output buffer limit (hard limit). 2012-01-25 18:11:04 +01:00