public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Cc: mr.jarry@gmail.com
Subject: Re: [gentoo-user] Tips for saving power needed...
Date: Mon, 2 Apr 2012 18:57:25 +0700	[thread overview]
Message-ID: <CAA2qdGXYfApSOYVjxiWB5Aq2WOwbpw3oP6AdgA4Ad0bx=2WCcw@mail.gmail.com> (raw)
In-Reply-To: <20120402115559.2b723512@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]

On Apr 2, 2012 5:00 PM, "Robert David" <robert.david.public@gmail.com>
wrote:
>
> Hi,
>
> maybe write your hw configuration first. Eg: CPUs, graphic cards, HDDs
> (size, speed, type) and others.
>
> Also provide lspci output and /proc/cpuinfo.
>
> Then this is a server, maybe with more than one GB nic. If you dont use
> spare nics disable them in bios. Do the same with other unneeded stuff.
>
> If you can access your server and replace cards, remove everything you
> dont need. Do not lower fans or dont play with cpu voltage. If you want
> to run this server 24/7 it can cause serious problems. It will not save
> you much power. Paradoxly this could lead to higher power usage in
> some cases, because of hotter devices.
>
> Remove spare memory cards, if you dont need much memory, etc.
>
> Robert.
>
> V Sun, 01 Apr 2012 17:04:58 +0200
> Jarry <mr.jarry@gmail.com> napsáno:
>
> > Hi,
> >
> > admin of a colo-center keeps complaining my server is going
> > a little over power-limit (which they have set as ~120W per
> > 24h/avg, while my server needs ~130-135W). So I need to find
> > a way to save at least those 15W, or I will be moved to
> > higher tarif (which means higher costs for server-housing).
> >
> > Before going hard(ware) way, I would like to try first
> > all possible software solutions. What I tried up to now is
> > cpufreqd, CONFIG_NO_HZ=y, and spindown. In addition to that
> > I adjusted fan-speeds to a little lower values and turned
> > off some unneeded peripherials (in bios).
> >
> > Is there anything else I could do? Any tips would be greatly
> > welcomed...
> >
> > Jarry
> >
>
>

I'd rather have *more* RAM than causing unnecessary swaps.

Try using a smaller swapfile to reduce swap tendencies. You can always push
a larger swapfile into service when needed.

There's also a kernel knob to set 'swappiness', but I forget what exactly.
Try 'sysctl -a | grep swap'

Rgds,

[-- Attachment #2: Type: text/html, Size: 2514 bytes --]

  reply	other threads:[~2012-04-02 11:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01 15:04 [gentoo-user] Tips for saving power needed Jarry
2012-04-01 15:24 ` Michael Hampicke
2012-04-01 15:56 ` Volker Armin Hemmann
2012-04-02  5:22   ` Walter Dnes
2012-04-06 17:05     ` [gentoo-user] Tips for saving power needed... particulary on laptops Frank Steinmetzger
2012-04-06 17:17       ` Michael Mol
2012-04-02  9:55 ` [gentoo-user] Tips for saving power needed Robert David
2012-04-02 11:57   ` Pandu Poluan [this message]
2012-04-02 12:10     ` Michael Mol
2012-04-02 14:17       ` Simon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA2qdGXYfApSOYVjxiWB5Aq2WOwbpw3oP6AdgA4Ad0bx=2WCcw@mail.gmail.com' \
    --to=pandu@poluan.info \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=mr.jarry@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox