http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660"In the first example, we have to assume that every read is the last read" That doesn't sound right to me. Generally when working with a rotating disks (but not limited to), you generally prefetch and use buffers in order to avoid disk seeks, even if this means fetching more data than necesary. What's the basis for aforementioned assumtion?http://ayende.com/154529/performance-implications-of-method-signatures#comment11http://ayende.com/154529/performance-implications-of-method-signatures#comment11Wed, 04 Apr 2012 06:50:03 GMTI still don't understand. If you are streaming data, just get the first batch and wait until they have consumed enough the trigger the next batch. You don't need to know how many batches will be fetched in total since you are only reading them on demand. If you are not streaming data, then you shouldn't be using IEnumerable.http://ayende.com/154529/performance-implications-of-method-signatures#comment10http://ayende.com/154529/performance-implications-of-method-signatures#comment10Tue, 03 Apr 2012 22:14:27 GMTSo, did you just prove that having more information is better than having less?http://ayende.com/154529/performance-implications-of-method-signatures#comment9http://ayende.com/154529/performance-implications-of-method-signatures#comment9Tue, 03 Apr 2012 21:42:42 GMTWhy user should decide it? What if I want just "default" number of results? Moreover this repository-like interface is too restrictive. How can I get documents after eTag starting with some prefix?http://ayende.com/154529/performance-implications-of-method-signatures#comment8http://ayende.com/154529/performance-implications-of-method-signatures#comment8Tue, 03 Apr 2012 17:03:39 GMTI believe the point is to force the user to decide how much data it wants. IQueryable won't help there.http://ayende.com/154529/performance-implications-of-method-signatures#comment7http://ayende.com/154529/performance-implications-of-method-signatures#comment7Tue, 03 Apr 2012 15:04:56 GMTIf IQueryable is too heavy solution, then you can inplement your own ResultSet type and Linq extension methods.http://ayende.com/154529/performance-implications-of-method-signatures#comment6http://ayende.com/154529/performance-implications-of-method-signatures#comment6Tue, 03 Apr 2012 12:02:42 GMTPoul Foged: As Mark Seemann states in his blogpost (http://blog.ploeh.dk/2012/03/26/IQueryableIsTightCoupling.aspx), this is not always a good idea.http://ayende.com/154529/performance-implications-of-method-signatures#comment4http://ayende.com/154529/performance-implications-of-method-signatures#comment4Tue, 03 Apr 2012 11:30:52 GMTI also do not understand why you aren't going with an IQueryable approach. Can you explain why?http://ayende.com/154529/performance-implications-of-method-signatures#comment3http://ayende.com/154529/performance-implications-of-method-signatures#comment3Tue, 03 Apr 2012 11:27:41 GMTIMO. This is why IQueryable was invented; Lets the callee see the intentions of the the caller ... http://ayende.com/154529/performance-implications-of-method-signatures#comment2http://ayende.com/154529/performance-implications-of-method-signatures#comment2Tue, 03 Apr 2012 11:24:16 GMTMay I suggest that the original question was not clear - you asked what the implications for the methods, but the answer is about the implications for implementing those methods.http://ayende.com/154529/performance-implications-of-method-signatures#comment1http://ayende.com/154529/performance-implications-of-method-signatures#comment1Tue, 03 Apr 2012 10:28:52 GMT