Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The 1000 mulitplier was converting to seconds #97

Merged
merged 5 commits into from
Oct 13, 2016
Merged

Conversation

luben
Copy link
Contributor

@luben luben commented Sep 7, 2016

Indicate that the number is ops/ms not ops/s and another small fix.

Indicate that the number is ops/ms not ops/s and another small fix
@luben
Copy link
Contributor Author

luben commented Sep 7, 2016

What about releasing 0.4.2? I think we should switch to 0.5.0 for the Kryo-4.0.0 upgrade as the serialization is incompatible with previous releases.

There is a backward compatibility switch (for handling the generics in the FiledsSerializer). Do you think we should also add a flag so that we can upgrade to Kryo-4.0.0 but keep backward compatibility? I am not sure this would be enough as there are also new serializers for java8 optionals - they are used also by the new scala compiler backed (by default in 2.12, with a switch in 2.11).

I think a cleaner path forward is to declare backward incompatibility due to Kryo-4.0 and handling of the new Java 8 classes.

- don't include a mutable.HashMap value member in the tested maps:
  it's a constant factor tested separately

- add tests for Vector[Int] and Array[Int]
that the Unsafe serialization can create bugger
payloads but is faster in some cases
compose the pipeline up to a function only once
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants