﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Louis commented on Premature optimizations</title><description>The road to hell is paved with optimization
</description><link>http://ayende.com/3358/premature-optimizations#comment3</link><guid>http://ayende.com/3358/premature-optimizations#comment3</guid><pubDate>Tue, 10 Jun 2008 16:49:01 GMT</pubDate></item><item><title>Ayende Rahien commented on Premature optimizations</title><description>It would seem so, wouldn't it?
  
But that isn't what would tend to happen, I have set a short timeout value for the read, which means that if the data isn't available, I abort the request.
  
</description><link>http://ayende.com/3358/premature-optimizations#comment2</link><guid>http://ayende.com/3358/premature-optimizations#comment2</guid><pubDate>Mon, 09 Jun 2008 22:15:20 GMT</pubDate></item><item><title>Kevin Gadd commented on Premature optimizations</title><description>That does mean that you incur more thread contention, though, since in cases where the data isn't available you have to block a thread for the read operation.
  
  
Did you try checking the amount of data waiting on the socket before performing the read? If so, how did that work out?
</description><link>http://ayende.com/3358/premature-optimizations#comment1</link><guid>http://ayende.com/3358/premature-optimizations#comment1</guid><pubDate>Mon, 09 Jun 2008 22:09:58 GMT</pubDate></item></channel></rss>