Re: rrdtool performance tuning (fwd)
- From: Brooks Davis <brooks@xxxxxxxxxxx>
- Date: Tue, 30 Oct 2007 12:06:17 -0500
On Tue, Oct 30, 2007 at 12:32:42PM +0300, Dmitry Morozovsky wrote:
On Mon, 29 Oct 2007, Brooks Davis wrote:
BD> On Mon, Oct 29, 2007 at 11:13:09AM +0300, Dmitry Morozovsky wrote:
BD> >
BD> > [hmm, after thinking a bit I decided it would be more appropriate here, in
BD> > stable@]
BD> >
BD> > Dear colleagues,
BD> >
BD> > any hints to tune rrdtool with ~30k rrd files (approx 2k target devices)?
BD> >
BD> > machine is mostly IO-bound, showing 100% disk load with 8 or sometimes even 3
BD> > mB/s, 300-400 tps (it's 2 SATA300 disks in gmirror)
BD>
BD> Store it on a memory file system and take periodic snapshots. The format is
BD> hopeless for large numbers of updates. The ganglia port's startup scripts show
BD> an example of doing this.
I thought about this, but total size of these files is already more than
memory, and I'm not sure md would be suitable for this.
FWIW, this is the only work around ganglia users have found. You might
consider a solid state disk or one of the battery backed RAM cards
out there if adding more memory and switching to a 64-bit OS isn't an
option.
-- Brooks
Attachment:
pgpBPZBAk7zH9.pgp
Description: PGP signature
- References:
- rrdtool performance tuning (fwd)
- From: Dmitry Morozovsky
- Re: rrdtool performance tuning (fwd)
- From: Brooks Davis
- Re: rrdtool performance tuning (fwd)
- From: Dmitry Morozovsky
- rrdtool performance tuning (fwd)
- Prev by Date: Re: RFC: Evolution of the em driver
- Next by Date: em watchdog problem
- Previous by thread: Re: rrdtool performance tuning (fwd)
- Next by thread: Re: rrdtool performance tuning (fwd)
- Index(es):