with my i7 920 I notice a reasonable difference after I enable irqbalance... especially with multimedia... so I wouldn't call it just enterprise.. but other than that I agree... Though I have been thinking about making my own spin for office work...
On Tue, Sep 20, 2011 at 3:33 PM, Toderel Adrian-Aurel <[email protected]>wrote: > irqbalance look like an enteprise feature, lots of procs and multipath > storages ... same thing for microcode update, this things maybe is useful > for hard stressed servers but for us if our processor is just working then > keep it happy and don't stress it more with unexpected fancy microcode > patches ... and microcode blobs to be useful needs an external and automatic > download/updating mechanism, something like a cronjob to check for new > microcodes and this look like an enterprise server setup again ... > > so, if you need an enterprise ready sabayon spin why to not just make one? > > Use Molecule to create your own > spin<https://forum.sabayon.org/viewtopic.php?f=87&t=24895> > > with irqbalance + microcode + ldap + kerberos = centralized mass deployment > and user rights management ? here if you can find something like Active > Directory in linux world you will spin for free something that is sell for > many $$$ even in linux world! this is why redhat and suselinux can make > money selling free software as enterprise linux packages! > > ======================================= > linux is free, but needed expertise to use this little beast > is a personal, time consuming, continuous accumulation of knowledge > and wasted time can not be rolled back no matter how much money you have > > selling free software can not bring to you too much money, > but USING free software you can make a lot of money > like Google ... or IBM > > your little help to free software development does not bring > to you any money but can help you use it more efficiently, > so you can make more money ... meanwhile, other users of > that little free software program, using your contribution > can make more money! nobody loses anything, all those who know > how to use a free software program, in continuous evolution, wins > registered linux user #352479 > > > > 2011/9/17 Lorenzo Cogotti <[email protected]> > >> As far as I know the main benefits are fixes in the CPU microcode, as >> basically the service will update the CPU microcode with more recent >> versions, if necessary. >> I don't know if this could bring also some performance improvements or >> better powersaving. I doubt that the kernel already handles this, since >> the microcode data is shipped by Intel or AMD themselves. >> As far as I understand from the AMD documentation, the microcode update >> is performed by the microcode module and I don't recall it being running >> in any AMD installation, so I would exclude that the microcode update is >> automatically handled by the kernel. >> As far as I can tell from the services files and lsmod output, that >> module is also needed for microcode_ctl, and it wasn't running before I >> activated that service (actually, if there is no change in >> the /etc/conf.d/microcode_ctl file, that module will be unloaded as soon >> as the first microcode update is performed). >> >> I would add it to the boot rulevel since this operation should be >> performed early in the boot sequence, but I don't think that it would >> hurt putting it in the default runlevel. >> >> Also, usually any Linux distribution (like OpenSuSE, for example) >> usually has it active by default. >> >> On a separate note, another related service that could be useful is: >> /etc/init.d/irqbalance >> and usually that service is enabled by default on other distributions >> too. >> Of course I don't mean that just because other distros do enable it, we >> should too :) >> >> Il giorno sab, 17/09/2011 alle 15.10 +0200, Fabio Erculiani ha scritto: >> > I've been always resilient to the addition of new boot services. >> > >> > What are the benefits of having microcode updates? Just CPU bug fixes? >> > I never felt the need of updating the microcode of my CPU actually. >> > Isn't it something that the kernel already takes care of? >> > >> >> -- >> Lorenzo Cogotti >> >> >> > > > >
