StephanEwen commented on issue #10358: [FLINK-14346] [serialization] faster 
implementation of StringValue writeString and readString
URL: https://github.com/apache/flink/pull/10358#issuecomment-561655258
 
 
   @shuttie Got it, makes a lot of sense to me.
   
   I was wondering at some point if it would be worthwhile to just "unsafe 
arraycopy" the char[] from the string to the byte[] in the memory segments or 
stream buffers. So basically no byte-wise logic at all in the serialization. 
That would increase the state size (all chars would have two bytes), but might 
save CPU resources.
   
   Have you ever experimented with something that?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to