Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17295
> What's the actual difference? previously we transfer encrypted data?
Yes. The previous version of the code would transfer the encrypted file
over to the receiver, and the encrypted data for serialized blocks would also
be stored in `MemoryStore` (and then decrypted on every use). That means the
files could just be mmap'ed for transfer, which is faster than the
`ReadableByteChannel` path even without encryption in the picture. (If you
consider the previous code had to decrypt from the `MemoryStore` on every read,
you can end up with better performance overall with this patch.)
But this caused all the other issues with making the `BlockManager` harder
to use when encryption was on, so I think this is a better solution.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
