Net/ftp is CPU bound


(jheard) #1

I was noticing the other day that FTPing large files over fast
connections like a 100 megabit ethernet inside a LAN causes my CPU usage
to go to 100% in no time, and I’m running a P3 933. I was wondering if
it would be good for me to add put/getbinaryfile and put/gettextfile
procedures that don’t pass their data to blocks and perhaps memory map
and/or buffer their transactions. If this is a good idea, what should
the procedures be named


(HAL 9000) #2

I was noticing the other day that FTPing large files over fast
connections like a 100 megabit ethernet inside a LAN causes my CPU usage
to go to 100% in no time, and I’m running a P3 933. I was wondering if
it would be good for me to add put/getbinaryfile and put/gettextfile
procedures that don’t pass their data to blocks and perhaps memory map
and/or buffer their transactions. If this is a good idea, what should
the procedures be named

Interesting idea. Maybe just add a
flag defaulting to false? That way:
No new method names, no broken code.

Just a thought.

Hal Fulton

···

----- Original Message -----
From: “jheard” jheard@acxiom.com
Newsgroups: comp.lang.ruby
To: “ruby-talk ML” ruby-talk@ruby-lang.org
Sent: Wednesday, June 05, 2002 4:21 PM
Subject: net/ftp is CPU bound