[ https://issues.apache.org/jira/browse/KUDU-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-832: ----------------------------- Target Version/s: (was: 1.5.0) > consider "sloppy" memcpy for better performance > ----------------------------------------------- > > Key: KUDU-832 > URL: https://issues.apache.org/jira/browse/KUDU-832 > Project: Kudu > Issue Type: Improvement > Components: perf > Affects Versions: 1.2.0 > Reporter: Todd Lipcon > Priority: Major > Attachments: test.cc > > > On the read path, a very high percentage of our time is spent in memcpy. > Typically, we are copying data to and from large allocations (eg from a data > block into a column block, or from a data block into a rowblock's arena, or > from an MRS arena into either of the above). In pretty much all of these > cases, it would be easy to ensure that the source and destination both have > at least 8 bytes of "padding" past the last valid value, and then round all > of our memcpys up to the nearest 8 bytes (even if the amount to be copied is > much smaller). This enables a really tight and fast memcpy loop, which > microbenchmarks indicate could be 40-50% faster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)