| |||||||||||||
All hail the speed demons (O'Reillynet)All hail the speed demons (O'Reillynet)Posted Nov 2, 2005 21:35 UTC (Wed) by darthmdh (guest, #8032)In reply to: All hail the speed demons (O'Reillynet) by alq666 Parent article: All hail the speed demons (O'Reillynet) For instance stripping .comment out of the binaries strikes me as a shot in the dark; I'm not sure whether mapping an extra 400k in memory is such a huge performance hit... When you have 20-odd shared libraries linked in with every application, that 400k soon becomes 8Mb. Even if it was, all-up, 400k - what happens if that 400k of useless cruft then pushes the required memory over a page boundary? And the new required page due to memory pressure requires paging something else to disk? You may call this nit-picking but there's a variety of applications where there is substantial memory pressure (think so-called embedded devices like mobile phones, pda's and network appliances) where 8Mb can be 25% (or more) of your RAM.
(Log in to post comments)
All hail the speed demons (O'Reillynet) Posted Nov 2, 2005 22:59 UTC (Wed) by proski (subscriber, #104) [Link] My interpretation of "Saved 400k over all OO.o libraries by stripping the .comment sections" is that it was a total number for all the OO.o libraries together. I don't think most of those libraries are used in the same time, and it's hard to imagine what it would take to occupy 8M with .comment sections, considering that most applications (even Mozilla) use much fewer libraries that OO.o.
|
|||||||||||||