On Fri, 25 Aug 2000 12:19:24 -0400, Dan Sugalski wrote: >Code you don't call won't eat up any cache space, nor crowd >out some other code. And if you do call it, well, it ought to be in the cache. Probably a stupid question... But can't you group the code for the most often used constructs? So that, if one of those things is loaded in the cache, the others are in there with it? If all the less needed stuff is more at the back of the executable, it wouldn't even have to be loaded, most of the time. Besides, I'm more worried about unnecessarily loading 600k from disk, than from main memory to cache. For short-lived scripts, this loading overhead could be quite significant. -- Bart.
- Re: RFC 146 (v1) Remove socket function... Dan Sugalski
- Re: RFC 146 (v1) Remove socket function... David L. Nicol
- Re: RFC 146 (v1) Remove socket function... Dan Sugalski
- Re: RFC 146 (v1) Remove socket function... mooring
- Re: RFC 146 (v1) Remove socket function... Alan Burlison
- Re: RFC 146 (v1) Remove socket function... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket functions from core Stephen P. Potter
- Re: RFC 146 (v1) Remove socket functions from c... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions fr... Michael Maraist
- Re: RFC 146 (v1) Remove socket function... Dan Sugalski
- Re: RFC 146 (v1) Remove socket function... Bart Lateur
- Re: RFC 146 (v1) Remove socket function... Tom Christiansen
- Re: RFC 146 (v1) Remove socket function... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket function... Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions fr... David Corbin
- Re: RFC 146 (v1) Remove socket function... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions fr... Chaim Frenkel
- Re: RFC 146 (v1) Remove socket function... Dan Sugalski
- Re: RFC 146 (v1) Remove socket function... Tom Christiansen
- Re: RFC 146 (v1) Remove socket function... Uri Guttman
- Re: RFC 146 (v1) Remove socket functions from core Joe McMahon