ByteBuffer-based read API for DFSInputStream
Review Request #4184 - Created March 5, 2012 and updated
Posting patch to RB on behalf of Henry.
first pass looks good. A few questions: - do you have before/after benchmarks for the old TestParallelRead with this patch? ie make sure this patch doesn't regress performance of the "normal" array-based read path? - have you run the various randomized tests overnight or so to get good coverage of all the cases? I didn't look carefully at the libhdfs code, since you said offline there's another rev of that coming
can you add javadoc explaining this var (even though it's not new)?
I'd move this inside the if statement below. Then in the second "phase", re-declare it under that scope, since the "len" variable doesn't ever carry over between phases (and in fact becomes invalid)
Seems like this area could be optimized a bit to avoid the object creation here... In one case, slowReadBuff.remaining() <= len, in which case you can directly do buf.put(slowReadBuff). In the other case, you could probably save off the limit of slowReadBuff, lower the limit to len, do the read, then set the limit again.
this code's very similar to line 358-362. Can we extract a utility function which we could optimize as I mentioned above to avoid object allocation?
I think it might simplify things if you used this function only for the case where verifyChecksum == true. Then above, the non-checksummed read case would just call fillBuffer directly. What do you think? My reasoning is that this function is called 'readChunksIntoByteBuffer' implying that it always reads a multiple of checksum chunk size, which isn't really a requirement when not verifying checksums
maybe TRACE is more appropriate here. Also LOG.trace() inside
remove commented out code
I think it's worth making these actual static inner classes with names instead of anonymous, for prettier stack traces. I remember we discussed a few weeks back whether the creation of these lambdas would harm performance for short reads. Do you have any results for TestParallelRead performance for the lambda-based approach here vs the uglier approach
goofy empty clause. Other goofy indentation here.