Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #28507

Re: byte stream vs char stream buffer

From Roedy Green <see_website@mindprod.com.invalid>
Newsgroups comp.lang.java.programmer
Subject Re: byte stream vs char stream buffer
Date 2014-05-16 20:19 -0700
Organization Canadian Mind Products
Message-ID <4nkdn9proikbeju5oj42p8s88hnjmjq01e@4ax.com> (permalink)
References (4 earlier) <bt7jpaFa8d5U1@mid.individual.net> <eegtm9d1ijt1u9fttnjk7o7hnphf0a46td@4ax.com> <lknegc$d7h$1@dont-email.me> <6r21n95tbn8vfv3tuj141tlvsrarqqo7uc@4ax.com> <5370a05b$0$2902$e4fe514c@news.xs4all.nl>

Show all headers | View raw


On Mon, 12 May 2014 12:20:11 +0200, Silvio <silvio@internet.com>
wrote, quoted or indirectly quoted someone who said :

>It would be interesting to repeat this experiment with different 
>character encodings and see if using UTF-16 versus UTF-8 makes a 
>difference here.

With UTF-16 there are twice as many byte to read, but the 50% magic
ratio still prevails.

best 5 five trials shown.

Using a random sample data file of 209,715,200 chars 419,430,402
bytes.
Using aggregate buffersize of 65,536 bytes.
Using charset UTF-16

BufferedReader backed with BufferedInputStream ratio 0.10 buffsize
65536 bytes  2.64 seconds
BufferedReader backed with BufferedInputStream ratio 0.20 buffsize
65536 bytes  2.63 seconds
BufferedReader backed with BufferedInputStream ratio 0.30 buffsize
65536 bytes  2.64 seconds
BufferedReader backed with BufferedInputStream ratio 0.40 buffsize
65536 bytes  2.64 seconds
BufferedReader backed with BufferedInputStream ratio 0.50 buffsize <--
65536 bytes  2.64 seconds
BufferedReader backed with BufferedInputStream ratio 0.60 buffsize
65536 bytes  2.68 seconds
BufferedReader backed with BufferedInputStream ratio 0.70 buffsize
65536 bytes  2.71 seconds
BufferedReader backed with BufferedInputStream ratio 0.80 buffsize
65536 bytes  2.79 seconds
BufferedReader backed with BufferedInputStream ratio 0.90 buffsize
65536 bytes  2.70 seconds
HunkIO 2.70 seconds





Using a random sample data file of 209,715,200 chars 209,715,200
bytes.
Using aggregate buffersize of 65,536 bytes.
Using charset UTF-8
HunkIO 0.73 seconds
BufferedReader backed with BufferedInputStream ratio 0.10 buffsize
65536 bytes  0.89 seconds
BufferedReader backed with BufferedInputStream ratio 0.20 buffsize
65536 bytes  0.88 seconds
BufferedReader backed with BufferedInputStream ratio 0.30 buffsize
65536 bytes  0.88 seconds
BufferedReader backed with BufferedInputStream ratio 0.40 buffsize
65536 bytes  0.89 seconds
BufferedReader backed with BufferedInputStream ratio 0.50 buffsize <--
65536 bytes  0.83 seconds
BufferedReader backed with BufferedInputStream ratio 0.60 buffsize
65536 bytes  0.91 seconds
BufferedReader backed with BufferedInputStream ratio 0.70 buffsize
65536 bytes  0.92 seconds
BufferedReader backed with BufferedInputStream ratio 0.80 buffsize
65536 bytes  0.96 seconds
BufferedReader backed with BufferedInputStream ratio 0.90 buffsize
65536 bytes  0.92 seconds

There is something strange. UTF-16 should be faster to convert to
Strings, and at worst, taking twice as long for physical I/O.
-- 
Roedy Green Canadian Mind Products http://mindprod.com
Young man, in mathematics you don’t understand things.
You just get used to them. 
~ John von Neumann (born: 1903-12-28 died: 1957-02-08 at age: 53)

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-06 23:48 -0700
  Re: byte stream vs char stream buffer Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-05-08 13:30 +0000
    Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-09 09:34 -0700
      Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-10 13:18 -0700
        Re: byte stream vs char stream buffer Robert Klemme <shortcutter@googlemail.com> - 2014-05-10 23:24 +0200
          Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-10 16:08 -0700
            Re: byte stream vs char stream buffer Robert Klemme <shortcutter@googlemail.com> - 2014-05-11 16:02 +0200
              Re: byte stream vs char stream buffer markspace <markspace@nospam.nospam> - 2014-05-11 11:50 -0700
                Re: byte stream vs char stream buffer markspace <markspace@nospam.nospam> - 2014-05-11 12:10 -0700
                Re: byte stream vs char stream buffer Robert Klemme <shortcutter@googlemail.com> - 2014-05-11 21:34 +0200
                Re: byte stream vs char stream buffer markspace <markspace@nospam.nospam> - 2014-05-11 12:55 -0700
                Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-16 16:55 -0700
                Re: byte stream vs char stream buffer markspace <markspace@nospam.nospam> - 2014-05-16 17:36 -0700
                Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-16 19:52 -0700
              Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-16 16:37 -0700
          Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-10 17:21 -0700
            Re: byte stream vs char stream buffer Martin Gregorie <martin@address-in-sig.invalid> - 2014-05-11 09:05 +0000
              Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-12 02:07 -0700
                Re: byte stream vs char stream buffer Silvio <silvio@internet.com> - 2014-05-12 12:20 +0200
                Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-16 20:19 -0700
                Re: byte stream vs char stream buffer Roedy Green <see_website@mindprod.com.invalid> - 2014-05-18 05:28 -0700
                Re: byte stream vs char stream buffer Silvio <silvio@internet.com> - 2014-05-18 23:54 +0200

csiph-web