Re: Java deserialization - any best practices for performances?

2009-07-24 Thread Kenton Varda
On Thu, Jul 23, 2009 at 7:15 PM, alopecoid alopec...@gmail.com wrote: Hmm... that strikes me as strange. I understand that the Message objects are immutable, but the Builders are as well? I thought that they would work more along the lines of String and StringBuilder, where String is

Re: java string literal too long when initializing java.lang.String descriptorData

2009-07-24 Thread Kenton Varda
How annoying. I'll make sure this or something like it gets into the next release -- which I'm going to try to push next week. On Wed, Jul 22, 2009 at 8:36 AM, anonymous eric.pe...@hp.com wrote: Hello, I was not able to compile a Java file generated by protoc 2.10 from a rather big .proto

Re: java string literal too long when initializing java.lang.String descriptorData

2009-07-24 Thread Christopher Smith
Heh, I remember complaining about this to James when they first published the byte code spec. It was annoying then and continues to be annoying today. On 7/24/09, Kenton Varda ken...@google.com wrote: How annoying. I'll make sure this or something like it gets into the next release -- which

Re: Java deserialization - any best practices for performances?

2009-07-24 Thread Christopher Smith
The best way to think of it is: Builder : Java Message :: C++ Message : const C++ Message As far as performance goes, it is a common mistake to confuse C/C++ heap memory allocation costs to Java heap allocation. In the common case, allocations in Java are just a few instructions... comperable