Having read this page, I can’t believe that VB.Net has such a terrible performance when it comes to I/O.
Is this still true today? How does the .Net Framework 2.0 perform in terms of I/O (that’s the version I’m targeting)?
Share
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.
Having read this page, I can’t believe that VB.Net has such a terrible performance when it comes to I/O.
Is this still true today? How does the .Net Framework 2.0 perform in terms of I/O (that’s the version I’m targeting)?
Beware of shoddy benchmarks without peer review. The file I/O benchmark code uses the old VB6 compatibility I/O functions, PrintLine() and LineInput(). Yes, they are not cheap. The bench mark also doesn’t attempt to do anything to measure real I/O performance, it doesn’t flush the file system cache. Somewhat understandable perhaps, that would measure the speed of the disk and every language would perform the same, within 0.1% or so.