Skip to content
This repository was archived by the owner on Dec 31, 2020. It is now read-only.

Update to 0.6.7 #15

Merged
merged 6 commits into from
May 2, 2016
Merged

Update to 0.6.7 #15

merged 6 commits into from
May 2, 2016

Conversation

EronWright
Copy link
Collaborator

No description provided.

wrighe3 added 4 commits April 26, 2016 19:00
- introduce NetworkInference because the Inference object is proving
too big to use as a data flow element.
}
for(Class<?> c : KryoSerializer.ADDITIONAL_REGISTERED_TYPES) {
config.registerTypeWithKryoSerializer(c, (Class<? extends Serializer<?>>) (Class<?>) KryoSerializer.class);
Class<?> serializerClass = DEFAULT_SERIALIZERS.getOrDefault(c, (Class<?>) KryoSerializer.class);
config.registerTypeWithKryoSerializer(c, (Class<? extends Serializer<?>>) serializerClass);
}
}

static final Class<?>[] ADDITIONAL_REGISTERED_TYPES = { Network.class };
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I can tell there is no reason to register the Network object. Internally, all registering does is share the class name (string) among all instances of that particular class (which is slower). So pre-registering helps avoid this behavior, but since there is only ever one instance of the Network, I don't see how registering it will be any more efficient because there is only ever one of its type being serialized?

@EronWright EronWright merged commit b18a5f2 into master May 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants