I just noticed that our HTTP client is very slow. Consider this:
--8<---------------cut here---------------start------------->8---
(use-modules (web client)
(rnrs io ports)
(rnrs bytevectors)
(srfi srfi-11)
(ice-9 format))
(define %uri
"http://ftp.gnu.org/gnu/idutils/idutils-4.6.tar.xz";)
(with-fluids ((%default-port-encoding #f))
(let*-values (((start)
(gettimeofday))
((p)
(let ((s (open-socket-for-uri %uri)))
(setvbuf s _IONBF)
s))
((r h)
(http-get %uri
#:port p
#:streaming? #t
#:decode-body? #f))
((d len)
(let ((b (get-bytevector-all h)))
(values b (bytevector-length b)))
;; (let ((b (make-bytevector (* 5 (expt 2 20)))))
;; (values b
;; (get-bytevector-n! h b 0 (bytevector-length b))))
)
((end)
(gettimeofday))
((throughput)
(let ((duration (- (car end) (car start))))
(/ (/ len 1024.) duration 1.0))))
(format #t "~5,1f KiB/s (total: ~5,1f KiB)~%"
throughput (/ len 1024.))))
--8<---------------cut here---------------end--------------->8---
Here I get a throughput of ~60 KiB/s, vs. ~400 KiB/s for wget and curl.
Looking at the strace output reveals no real difference: they all make
one syscall for each chunk of 1410 bytes.
‘time’ reports that Guile spends 0.2 s. in user and 0.8 s. in system,
both of which are an order of magnitude higher than wget/curl.
Bypassing the custom binary input ports from http.scm and response.scm
doesn’t make any big difference. Forcing the zero-copy path in
‘scm_c_read’ doesn’t help much either.
Ideas?
Thanks,
Ludo’.
