I forgot to say that Our avro serializer is slower (1.6) than Java serialization esp when the VM is not warm (small loop value like = 1000 In evens up on longer loops like 100000
Our avro serializer is slower (2.5) than Java serialization esp when the VM is not warm (small loop value like = 1000 In evens up or beats the Java serialization on longer loops like 100000 However, Avro's message is half the size and there are some room for improvement. On 6 août 2011, at 14:31, Emmanuel Bernard wrote: > I'm done with the serialization protocol. At least, it's in a good shape and > should be integrated with trunk > > It uses Avro and is now integrated with both JGroups and JMS backends. > > I've abstracted Avro from our serialization logic so we can write alternative > prototypes. I'd be interested to see a Protocol Buffer alternative for > example. If anyone is interested, check out SerializationProvider and it's > inplementation AvroSerializationProvider > > Not everything is polished, I've created a list of follow up issues to be > fixed before 4.0. https://hibernate.onjira.com/browse/HSEARCH-757 > These a good candidates for community contribution. > > I have one minor question > Should hibernate.search.jms.indexNameProperty that be part of the protocol or > left separate like today? > > I'll send a pull request in the next few minutes > > Emmanuel > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev