|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| General Chit-Chat A friendly place to converse about your adventures with openSUSE, your weekend, your boss, your new car, and generally stuff that doesn't fit somewhere else (and we must ask: PLEASE do not post help questions here) |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
> So the question is - how much is possible to make OpenSuSE (or any
> other distro from the name of the topic) light, fast and efficient? that is kinda like asking: Q: Of all the automobiles manufactured today, how much is possible to make them light, fast and efficient? A: That depends on how much time and effort at rebuilding you intend to invest. As well as the level of your particular mechanical skills and tools set. so, back to your question and my A: All can be slimmed down to be lighter, faster and more efficient. another way to attack this problem would be to just pick an already light, fast and efficient distro and do NOT load it down trying to make it "look better" and have more eye-candy, bells and whistles and etc than the Redmond Pig. (which, imho, seems to be the focus of the current openSUSE/KDE4 development clique..) ymmv, -- brassy |
|
||||
|
I perfectly understand what are you talking about, but I meant how light, fast and efficient can they be with default packages. Of course, it is always possible to rebuild something with additional optimizations, but that is not quite smart and logical, since it is much easier to simply switch to another distro.
I.e. I've read few months ago that many people used alternate Ubuntu install CD and they built it manually (by using APT) installing just necessary stuff and results were quite amazing. That is why I'm interested if there are similar experiences with OpenSuSE. Also, I forgot to mention RAM usage: 1. sidux install with KDE 4.2.4 and ktorrent running 3 torrents, took only (believe it or not) 130 MB (I used free -m command). 2. for comparision, Fedora with KDE 4 and without additional software running is starting basically with 250 MB. |
|
|||
|
kukibl wrote:
> I meant how light, fast and efficient can they be with default packages. define "default packages"! to begin with there are <on http://software.opensuse.org/> THREE choices (32 bit, 64 bit and Power PC) then you can choose TWO disks (CD and DVD).. that give SIX "default packages".. AND, if you select CD above, THEN you can choose between Gnome or KDE4..giving, 3x2 more options.. BUT, if you select the DVD as your "default", THEN during install you can select from Gnome, KDE3, KDE5, XFCE, Minimal X Window, Minimal Server Selection, giving 3x6 options.. THEN, you can later in the install process you can add or delete the pigs you wish.. the answer to your question depends on what you consider "default". generally, they are faster, lighter and more efficient than sliced bread....next question! but, for a more definitive answer i'd suggest you install all the possible defaults, measure the weight, speed and efficiency or each and stuff the data into a OpenOffice.org Calc chart, complete with colored graphs.. -- brassy |
|
||||
|
Quote:
That is why I started this topic, to avoid that kind of experiment. It is time consuming and probably at the end of the day not that much necessary. I want to hear what other people experienced, I am sure that not everybody is using default choices (DVD, live CDs install) and add only software they need. I believe that there are lots of people who play with default selections, remove unnecessery packages and services, maybe even modify configuration files in order to get less bloated system. |
|
|||
|
Tweaking can only do so much.
Except for beagle, I don't find that turning off daemons does much, unless you are desperately short of memory. Their footprints are in the order of tens of MB. Firefox's footprint easily swamps that. Removing packages does nothing except free up some disk space, which is cheap these days. If you never use OO, it makes no difference removing its packages. Fast graphics cards, fast disks and controller, fast CPU, and most important, sufficient memory help a lot. Compilation optimisation a la Gentoo may get you some increase in speed but I'm not prepared to have my machine grind away for hours just to get it. It may be worth it for some CPU intensive programs like encoders and media players, but those already use tricks to select the best code for the CPU. I'm not willing to use lighter but less capable versions of software just to be able to run faster, if it means I have to spend more time coping with lack of features I want. With hardware so cheap these days, over the lifetime of the computer the time wasted outvalues the saving in using a slower machine. |
|
||||
|
Quote:
...but - could somenone explain me why such difference between sidux and Fedora with basically same install (no additional services or daemons)? 100 MB is not small difference.Right now I'm running my sister's laptop (OpenSuSE 11.1) with minimal KDE3 and Firefox. It still looks slower compared to sidux with KDE4, but this impressed me: Code:
$free -m
total used free shared buffers cached
Mem: 1876 1777 98 0 90 1551
-/+ buffers/cache: 135 1740
Swap: 251 0 250
|
|
||||
|
as you can see, most of your memory is cached which is a good thing as free memory is useless and also it is faster when apps are cached in memory compared to always loading them from disk
further, KDE4 has a smaller memory footprint than KDE3 so a comparison here is not valid. Maybe Sidux compiles everything with -finline-functions which can make software run ~10% faster and which SUSE 11.2 will also use for all its packages. Presonally, on my machines, SUSE is very fast for me
__________________
My site: http://microchip.bplaced.net My repo: http://download.opensuse.org/repositories/home:/microchip8 SUSE Unbound Forum: http://suseunbound.lefora.com Do coders dream of sheep() ? |
|
||||
|
Quote:
Quote:
Anyway, my comparision was between Fedora and sidux, both running KDE4. |
|
|||
|
You just quoted some numbers for sidux and Fedora without saying how you measured them. You should be looking at the line:
-/+ buffers/cache and without any apps running in the GUI. Also on the exact same hardware, because the footprint of the X server depends on what drivers are used. Also some of the video memory that's mapped in is also counted in the X server's footprint. So unless you are careful in what you are measuring, that 100MB may be significant, or not. |
![]() |
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|