On Mon, Feb 25, 2013 at 8:42 PM, Yonik Seeley <yo...@lucidworks.com> wrote: > > > That's.... insane! >
It is insane. Keep in mind this was a 5-node cluster on the same physical machine sharing the same resources. It consist of 5 smartos zones on the same global zone. On my MacBook Pro I saw ~1.5ms per stale check but that was not under load (I'm honestly not sure if on/off load makes a difference as it didn't seem to on my smartos cluster). I could probably get to the root of this with DTrace/BTrace, but alas I haven't bothered. > > It's still not even clear to me how the stale check works (reliably). > Couldn't the server still close the connection between the stale check > and the send of data by the client? > The stale check isn't 100%, but it works most of the time. As you say, the server could close the socket between the stale check completing and the request data being sent. I'm pretty sure Oleg, one of the maintainers, has said as much but I can't find the original context. -Z
