[
https://issues.apache.org/jira/browse/MINIFI-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882955#comment-15882955
]
ASF subversion and git services commented on MINIFI-199:
--------------------------------------------------------
Commit 7d3e0441342825255781d1800c0178046f34254f in nifi-minifi-cpp's branch
refs/heads/master from Marc Parisi
[ https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;h=7d3e044 ]
MINIFI-206: Implement Extensible Comm Mechanism
Create initial communication mechanism that's
initially based on BSD sockets.
MINIFI-201: Change how hostname is resolved
and ensure that it is not null
MINIFI-199: Utilize zlib's crc32 implementation,
which is more portable and faster. we can explore
alternatives when that time arrives.
MINIFI-200: Put host "get" into initialization.
Any change wouldn't be picked up by a running process
most likely.
This closes #54.
Signed-off-by: Aldrin Piri <[email protected]>
> CRC32 Implementation is inefficient
> -----------------------------------
>
> Key: MINIFI-199
> URL: https://issues.apache.org/jira/browse/MINIFI-199
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Components: C++
> Reporter: marco polo
> Fix For: cpp-0.2.0
>
>
> The CRC32 Impl in Site2Site is 4x slower than a custom thread safe
> implementation and approximately 200x slower than zlib. We should probably
> opt for zlib's implementation. The pure C++ implementation is also an option
> if there are potential concerns for portability.
> I do think the bigger issue will be maintenance as zlib's implementation is
> well accepted and platform independent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
