in Wen
--
发件人：Chen Liang
发送时间：2025年6月30日(周一) 14:07
收件人："温绍锦(高铁)"
抄 送：Brett Okken;
"core-libs-dev"
主 题：Re: Eliminate unnecessary buffering and encoding conversion in
BufferedWriter
Brainstorming time:
I think Brett's suggestion makes sense: Buffere
发件人：Alan Bateman
发送时间：2025年6月30日(周一) 13:38
收件人："温绍锦(高铁)";
"core-libs-dev"
主 题：Re: Eliminate unnecessary buffering and encoding conversion in
BufferedWriter
On 29/06/2025 17:03, wenshao wrote:
BufferedWriter -> OutputStreamWriter -> StreamEncoder
In this call
when using LATIN1 String, and
> the performance will not be good.
>
> --
> 发件人：Brett Okken
> 发送时间：2025年6月30日(周一) 11:39
> 收件人："温绍锦(高铁)"
> 抄 送："core-libs-dev"
> 主 题：Re: Eliminate unnecessary bu
On 29/06/2025 17:03, wenshao wrote:
BufferedWriter -> OutputStreamWriter -> StreamEncoder
In this call chain, BufferedWriter has a char[] buffer, and
StreamEncoder has a ByteBuffer. There are two layers of cache here, or
the BufferedWriter layer can be removed.
LATIN1 (byte[]) -> UTF16 (ch
> BufferedWriter -> OutputStreamWriter -> StreamEncoder
>
> In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has
> a ByteBuffer. There are two layers of cache here, or the BufferedWriter layer
> can be removed. And when charset is UTF8, if the content of write(String) is
On Fri, 27 Jun 2025 16:48:40 GMT, Shaojin Wen wrote:
> BufferedWriter -> OutputStreamWriter -> StreamEncoder
>
> In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has
> a ByteBuffer. There are two layers of cache here, or the BufferedWriter layer
> can be removed. And w
On Fri, 27 Jun 2025 16:48:40 GMT, Shaojin Wen wrote:
> BufferedWriter -> OutputStreamWriter -> StreamEncoder
>
> In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has
> a ByteBuffer. There are two layers of cache here, or the BufferedWriter layer
> can be removed. And w
On Fri, 27 Jun 2025 16:48:40 GMT, Shaojin Wen wrote:
> BufferedWriter -> OutputStreamWriter -> StreamEncoder
>
> In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has
> a ByteBuffer. There are two layers of cache here, or the BufferedWriter layer
> can be removed. And w
On Fri, 27 Jun 2025 16:48:40 GMT, Shaojin Wen wrote:
> BufferedWriter -> OutputStreamWriter -> StreamEncoder
>
> In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has
> a ByteBuffer. There are two layers of cache here, or the BufferedWriter layer
> can be removed. And w
BufferedWriter -> OutputStreamWriter -> StreamEncoder
In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has a
ByteBuffer. There are two layers of cache here, or the BufferedWriter layer can
be removed. And when charset is UTF8, if the content of write(String) is
LATIN1,
.
--
发件人：Brett Okken
发送时间：2025年6月30日(周一) 11:39
收件人："温绍锦(高铁)"
抄 送："core-libs-dev"
主 题：Re: Eliminate unnecessary buffering and encoding conversion in
BufferedWriter
Maybe another option would be to implement BufferedWriter with a StringBuilder
rather than a char[
Maybe another option would be to implement BufferedWriter with a
StringBuilder rather than a char[]. This would remove the force to utf-16
On Sun, Jun 29, 2025 at 10:36 PM Brett Okken
wrote:
> Is StreamEncoder buffering content to only write to the underlying
> OutputStream when some threshold i
Is StreamEncoder buffering content to only write to the underlying
OutputStream when some threshold is hit? While the layers of conversions
are unfortunate, it seems there could be negative performance implications
of having many extremely small writes (such as 1 character/byte) at a time
to the un
BufferedWriter -> OutputStreamWriter -> StreamEncoder
In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has a
ByteBuffer. There are two layers of cache here, or the BufferedWriter layer can
be removed.
LATIN1 (byte[]) -> UTF16 (char[]) -> UTF8 (byte[])
And when charset is
14 matches
Mail list logo
