[issue21638] Seeking to EOF is too inefficient!

Charles-François Natali added the comment: I agree that Python 2 should use fopen / fread rather than directly read(). But you may misunderstand this. The 'strace' tool reports Linux system calls, including read() rather than fread(), and I guess that read() should be finally called in

[issue21638] Seeking to EOF is too inefficient!

Linlin Yan added the comment: Thanks! I agree with that. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21638 ___ ___ Python-bugs-list mailing

[issue21638] Seeking to EOF is too inefficient!

Linlin Yan added the comment: I ensured that the problem is in libc. I will try to figure out it by updating libc or optimizing some related parameters. -- resolution: - third party status: open - closed ___ Python tracker rep...@bugs.python.org

[issue21638] Seeking to EOF is too inefficient!

New submission from Linlin Yan: I noticed this problem when I run a Python2 program (MACS: http://liulab.dfci.harvard.edu/MACS/) very inefficiently on a large storage on a high performace server (64-bit Linux). It was much slower (more than two days) than running it on a normal PC (less than

[issue21638] Seeking to EOF is too inefficient!

STINNER Victor added the comment: I don't think that Python calls directly read(). Python 2 uses fopen / fread. Python 3 doesn't use buffered files, but call open / read directly. -- nosy: +haypo, neologix ___ Python tracker rep...@bugs.python.org

[issue21638] Seeking to EOF is too inefficient!

Linlin Yan added the comment: I agree that Python 2 should use fopen / fread rather than directly read(). But you may misunderstand this. The 'strace' tool reports Linux system calls, including read() rather than fread(), and I guess that read() should be finally called in fread()