Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40316654
Eh the other reason fastutil implements the FastByteArrayOutputStream
without subclassing ByteArrayOutputStream was to get rid of the synchronized
writes. To do this properly, we should probably benchmark every corner case to
see how well the jvm can do away with the lock that is always running in a
single threaded mode. However, we are not adding much code anyway so I think
this is good as is.
---
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.
---
