GitHub PushEvent at 2014-06-27 00:46:04
Repository: netty
Actor: idelpivnitskiy
Payload: {"shas":[["70f1ce3cdd15c604794a47220394077af80d9b1d","c6d25a6b3d6f79281fd6ef0a425a9dcf91b94750@redhat.com","Fix buffer leaks in Bzip2DecoderTest","Norman Maurer",false],["6e411fd04d39b32d3804cc2a9315a832c1c1a55d","2f270068e233b73e2851ed34f2d5f830d4899cd2@fb.com","Improve the allocation algorithm in PoolChunk\n\nMotivation:\n\nDepth-first search is not always efficient for buddy allocation.\n\nModification:\n\nEmploy a new faster search algorithm with different memoryMap layout.\n\nResult:\n\nWith thread-local cache disabled, we see a lot of performance\nimprovment, especially when the size of the allocation is as small as\nthe page size, which had the largest search space previously.","Pavan Kumar",false],["d0569ff53e379e26cbd4d60593ef7e65969efdd3","8efd86fb78a56a5145ed7739dcb00c78581c5375@motd.kr","Fix inspector warnings","Trustin Lee",false],["e473c19e9d02bbd5a117f1adfae10d976a8a3184","8efd86fb78a56a5145ed7739dcb00c78581c5375@motd.kr","Optimize PoolChunk\n\n- Using short[] for memoryMap did not improve performance. Reverting\n  back to the original dual-byte[] structure in favor of simplicity.\n- Optimize allocateRun() which yields small performence improvement\n- Use local variable when member fields are accessed more than once","Trustin Lee",false],["bab50a977788c1d8b6d5373aecfe48524d44951d","8efd86fb78a56a5145ed7739dcb00c78581c5375@motd.kr","Fix buffer leaks in Bzip2Decoder(Test)\n\nIf decompression fails, the buffer that contains the decompressed data\nis not released.  Bzip2DecoderTest.testStreamCrcError() also does not\nrelease the partial output Bzip2Decoder produces.","Trustin Lee",false],["07a1983f27b7af842adfc18c34a3ca0450253483","8efd86fb78a56a5145ed7739dcb00c78581c5375@motd.kr","Checkstyle","Trustin Lee",false],["c4d94a52cde4408e2fcc0e55d0286ab51b61d3ef","c6d25a6b3d6f79281fd6ef0a425a9dcf91b94750@redhat.com","Reduce the memory copies in JdkZlibEncoder\n\nMotivation:\n\nAt the moment we use a lot of unnecessary memory copies in JdkZlibEncoder. This is caused by either allocate a to small ByteBuf and expand it later or using a temporary byte array.\nBeside this the memory footprint of JdkZlibEncoder is pretty high because of the byte[] used for compressing.\n\nModification:\n\n- Override allocateBuffer(...) and calculate the estimatedsize in there, this reduce expanding of the ByteBuf later\n- Not use byte[] in the instance itself but allocate a heap ByteBuf and write directly into the byte array\n\nResult:\n\nLess memory copies and smaller memory footprint","Norman Maurer",false],["bfd7e510ac0d1dcca8770efb08a4dcb27ec678c8","8efd86fb78a56a5145ed7739dcb00c78581c5375@motd.kr","Fix incorrect bytesBefore/indexOf() in ReplayingDecoderBuffer\n\nMotivation:\n\nbytesBefore(length, ...), bytesBefore(index, length, ...), and\nindexOf(fromIndex, toIndex,...) in ReplayingDecoderBuffer are buggy.\nThey trigger 'REPLAY even when they don't need to.\n\nModification:\n\nImplement the buggy methods properly so that REPLAYs are not triggered\nunnecessarily.\n\nResult:\n\nCorrect behvaior","Trustin Lee",false],["d3dbeace1503495be56e80a9e8903ac84da18b02","c6d25a6b3d6f79281fd6ef0a425a9dcf91b94750@redhat.com","[#2605] Use SO_REUSEADDR on EpollServerSocketChannel to match defaults of java.nio.ServerSocketChannel impl\n\nMotivation:\n\nWhen using openjdk and oracle jdk's nio (while using the nio transport) the ServerSocketChannel uses SO_REUSEADDR by default. Our native transport should do the same to make it easier to switch between the different implementations and get the expected result.\n\nModification:\n\nChange EpollServerSocketChannelConfig to set SO_REUSEADDR on the created socket.\n\nResult:\n\nSO_REUSEADDR is used by default on servers.","Norman Maurer",false],["f08848da7c1dad72ca2304f9b24db0bec5ca551f","c6d25a6b3d6f79281fd6ef0a425a9dcf91b94750@redhat.com","[#2598] Add Epoll.isAvailable() which allows to check if epoll can be used.\n\nMotivation:\n\nAt the moment there is no simple way for a user to check if the native epoll transport can be used on the running platform. Thus the user can only try to instance it and catch any exception and fallback to nio transport.\n\nModification:\n\nAdd Epoll.isAvailable() which allows to check if epoll can be used.\n\nResult:\n\nUser can easily check if epoll transport can be used or not","Norman Maurer",false],["af042bb7d2afca348948a9dbada1f13da58a5fb7","c6d25a6b3d6f79281fd6ef0a425a9dcf91b94750@redhat.com","Add missing @Test annotation","Norman Maurer",false]],"size":11,"ref":"refs/heads/master","head":"af042bb7d2afca348948a9dbada1f13da58a5fb7"}