 |
Puppy Linux Discussion Forum Puppy HOME page : puppylinux.com "THE" alternative forum : puppylinux.info
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in|
The time now is Sat 15 Dec 2018, 17:27 All times are UTC - 4 |
 Forum index » Advanced Topics » Cutting edge |
|
system optimization techniques
Moderators: Flash, Ian, JohnMurga |
 
|
View previous topic :: View next topic |
| Page 1 of 2 [26 Posts] | Goto page: 1, 2 Next |
| Author | Message | ||||||||
|---|---|---|---|---|---|---|---|---|---|
technosaurus
 Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
Wondering whether or not to recompile a program in your puplet to eliminate large shared libs that are only used once or twice
this will tell you how many times each library is needed (if it isn't on the list, it can likely just be removed --- not always though, need to remember dlopen and/or plugins may use it too ... in "module" mode) now open binaudit in your text editor and get to work, starting with the ones that are needed only once ... you can build them in statically The ones that are used the most would benefit the most tools by improving their compiles (I will discuss that later) I'll go over optimization techniques soon. _________________ Check out my github repositories. I may eventually get around to updating my blogspot. |
||||||||
|
|||||||||
 |
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
Reserved compile techniques. In case you ever wondered whether or not to set certain flags, it is helpful to know which ones already are set. This can be done by:
CFLAGS -Os (optimize for speed unless it will increase size) -finline-small-functions (inline if it is smaller to inline than call it) -finline-functions-called-once -fearly-inline (requires gcc update) -ffunction-sections -fdata-sections with -Wl,--gc-sections LDFLAG pdf explanation by Denys Vlasenko (busybox maintainer) (allows compiler to remove functions and data that aren't actually used even if they are in the same object file as one that is) -fno-unwind-tables -fno-asynchronous-unwind-tables (don't include unnecessary unwind info)
LDFLAGS --gc-sections (see above) --as-needed (don't explicity link all libraries passed on the command line - try to see if any are useless ... all the locations of functions accessed indirectly via direct dependencies get stored in the binary when they can be loaded at runtime much more effectively - assuming the libraries get updated periodically, the locations will all be wrong and take much much longer to load) NOTE: gcc should have a --warn-as-needed to inform developers which libraries are unneeded when their crappy build scripts are broken _________________ Check out my github repositories. I may eventually get around to updating my blogspot. Last edited by technosaurus on Tue 09 Oct 2012, 01:26; edited 5 times in total |
||||||||
|
|||||||||
|
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
Shrinking files. _________________ Check out my github repositories. I may eventually get around to updating my blogspot. |
||||||||
|
|||||||||
|
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
Boot speed. 0. Do as little as necessary. and put off stuff not necessary to start X into xinit (you really only _need_ to mount /proc, /sys, /dev and the rootfs) 1. run as much as possible in parallel & a. if there are no prerequisites to running a command/function and it is not a prerequisite to others, then you can just add a & to the end.
b. if there are prerequisites involved, use the builtin $! variable to store the PID(s) (technically job IDs) of a parallel command(s), so that you can use the wait command to ensure the prerequisite calls are complete.
This method can be even more effective than systemd's pathetic parallel-ization methods 2. avoid unnecessary sleep(s) or at least unnecessarily long ones a. use an appropriate check or wait command instead where possible with short sleeps in a loop rather than just using really long sleeps
3. use busybox (or toybox) instead of GNU utils, they are smaller, so they load faster and the shells are about 4x faster than bash 4. when operating on strings, variables or even small files(< ~100 lines) use the shell's substring manipulation and other builtins instead of external utilities like awk, grep, sed, tr, which see http://www.murga-linux.com/puppy/viewtopic.php?t=70238 5. minimize unnecessary files in your initramfs/rootfs... One or two large files compress better (and load faster) than many smaller files - its better to include all the functions in the init script or at least a single function header than to use a bunch of smaller ones. This speeds up load times in the initramfs because it compresses better and reduces seek and load times in both the initramfs and rootfs (especially if the rootfs is on a slower or fragmented disk drive). If a kernel module is needed in the init, chances are it should be builtin. Similarly shared libraries add additional bloat and load time (for multiple reasons), a static busybox built against musl or uclibc can significantly cut down load times. The popular rant against static builds in favor of shared libraries by Ulrich Drepper is backed up by metrics based on glibc (which he maintained) which is horribly suited for static builds (a simple static hello world is over 400kb) see https://sta.li/faq 6. use tools like bootchartd, strace and lsof to measure the files used and times spent in various sections and the order, you can use this to "readahead" files that will be used and to order the filesystem so that files are in sequential order 7. use kernel parameters libahci.ignore_sss=1 #spin up disks in parallel instead of series quiet #eliminates superfluous messages from the console loglevel=3 #or less... only log the most critical issues the lower the number, the fewer log messages #probably more 8. don't write unnecessary stuff to the console ... or if you must, write as much as possible at once (for example, use a single success/fail message that handles multiple items instead of doing them one ata time). printf is useful for this Last edited by technosaurus on Mon 09 Oct 2017, 19:38; edited 1 time in total |
||||||||
|
|||||||||
|
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
X _________________ Check out my github repositories. I may eventually get around to updating my blogspot. |
||||||||
|
|||||||||
|
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
Alternative apps/libs _________________ Check out my github repositories. I may eventually get around to updating my blogspot. |
||||||||
|
|||||||||
|
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
Kernel configs _________________ Check out my github repositories. I may eventually get around to updating my blogspot. |
||||||||
|
|||||||||
|
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
Portability _________________ Check out my github repositories. I may eventually get around to updating my blogspot. |
||||||||
|
|||||||||
|
|||||||||
sunburnt
 Joined: 08 Jun 2005 Posts: 5087 Location: Arizona, U.S.A. |
Hi technosaurus; I wondered if this could do a statistical analysis of lib. usage in common apps. I did a sudo analysis myself that showed a small percentage of libs. are actually in common use. This is all about rules for which libs. to include in static builds. Once the libs. are identified, then scripts for statically building them. I don`t know if a build script "scrap" can be used many times like this. |
||||||||
|
|||||||||
|
|||||||||
|
scsijon
Joined: 23 May 2007 Posts: 1364 Location: the australian mallee |
Technosaurus, I wonder if a common lib could be built, something on the Busybox basis? It should shrink the overall size a bit! |
||||||||
|
|||||||||
|
|||||||||
|
disciple
Joined: 20 May 2006 Posts: 6867 Location: Auckland, New Zealand |
FWIW there was a project to build GTK and X and stuff all into one binary... but it seems to be dead. _________________ Do you know a good gtkdialog program? Please post a link here Classic Puppy quotes ROOT FOREVER GTK2 FOREVER |
||||||||
|
|||||||||
|
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
Goingnuts and I have done several x11, xaw and gtk1 apps as multicall binaries.... Gtk2 apps tend to use plugins - thus requiring significant patches... However there is an in between method where you mix static and dynamic libs based on analysis of dependencies. It gets complicated when you have to build pic versions of static libs so they can be statically linked into plugins (like png for imlib) and further complicated if you have another app that links to those libs directly (such as jwm with png support) requires changing the build to link to the imlib plugins for jwm. This is fine if you are doing a 1 time build of an embedded system with limited resources, but a royal pain to maintain for a distro. Thus the reason we hand picked a few compatible apps (sometimes even specific versions) and limited them to the minimum functionality needed to use/build/rebuild a system either from scratch using any distro's packages or so that if your whole shared library system gets corrupted, you can still recover comfortably with an intact desktop environment and still do basic everyday tasks like editing text, browsing the web or your file system, answering email and of course wasting time even if your libc gets corrupted. _________________ Check out my github repositories. I may eventually get around to updating my blogspot. |
||||||||
|
|||||||||
|
|||||||||
|
sunburnt
Joined: 08 Jun 2005 Posts: 5087 Location: Arizona, U.S.A. |
I see no point in BusyBox in Squash file based O.S.s. It just ends up being double compressed, usually with little improvement. And here at Puppy we know BusyBox commands just don`t measure up. Thought it could be compiled with full spec. commands... BusyBox is a good idea for loose file systems, but not Squash file ones. |
||||||||
|
|||||||||
|
|||||||||
|
disciple
Joined: 20 May 2006 Posts: 6867 Location: Auckland, New Zealand |
What do you mean? Busybox isn't about compression, is it? _________________ Do you know a good gtkdialog program? Please post a link here Classic Puppy quotes ROOT FOREVER GTK2 FOREVER |
||||||||
|
|||||||||
|
|||||||||
|
technosaurus
Joined: 18 May 2008 Posts: 4844 Location: Blue Springs, MO |
The advantage of statically compiling a multicall binary is that unused functions get compiled out. Busybox also has the capacity to "prefer applets" and call them as a function or by forking itself (both are much faster than running a separate binary... even moreso if that binary has to find and load shared libs) the only compression is the help text. Really it wouldn't hurt much to put a full busybox in the initramfs and copy it over. The only reason busybox applets sometimes fail is because the scripts weren't specifically written for it (tinycore scripts all work because they were) But I did notice that upx slows busybox down and the extra compression is negligible. _________________ Check out my github repositories. I may eventually get around to updating my blogspot. |
||||||||
|
|||||||||
|
|||||||||
system optimization techniques
| Page 1 of 2 [26 Posts] | Goto page: 1, 2 Next |
|
|
View previous topic :: View next topic |
|
Forum index » Advanced Topics » Cutting edge |
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum |
Powered by phpBB © 2001, 2005 phpBB Group