Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have to craft a data processor able to process more than 2.5MB/s of input from STDIN, and output a number to STDOUT. What is faster, to use a BufferedReader and then conversions to data types or a Scanner and nextInt() or nextFloat()?
EMPIRICAL TEST RESULTS: BufferedReader and conversion is a little bit faster, but nothing too significant.
Thankyou!
The answer is most likely that it doesn’t matter which way you do it from a performance perspective. (And there’s no way that someone can type at 2.5Mb per second at the console!)
If you include everything that goes on at the OS level and elsewhere when reading from the console, orders of magnitude more CPU cycles will be expended in getting the bytes from the user typing at the console than are spent parsing the characters. If you are reading from a file (via stdin), we are no longer talking orders of magnitude difference, but I’d still be surprised if the two approaches were significantly different … overall.
But the best thing you can do is try it out. It shouldn’t take more than a few minutes to write a benchmark that roughly approximates to what you are doing, and see which alternative is faster … and by how much. (Make sure that you measure total elapsed time, not just user-space CPU time for the Java application.)