All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Hans Reiser <reiser@namesys.com>, PFC <lists@peufeu.com>,
	"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: Reiser4 und LZO compression
Date: Tue, 29 Aug 2006 14:11:06 -0500	[thread overview]
Message-ID: <44F4914A.1010005@slaphack.com> (raw)
In-Reply-To: <e692861c0608291136j6ae2293cha230575acf6c031d@mail.gmail.com>

Gregory Maxwell wrote:
> On 8/29/06, David Masover <ninja@slaphack.com> wrote:
> [snip]
>> Conversely, compression does NOT make sense if:
>>    - You spend a lot of time with the CPU busy and the disk idle.
>>    - You have more than enough disk space.
>>    - Disk space is cheaper than buying enough CPU to handle compression.
>>    - You've tried compression, and the CPU requirements slowed you more
>> than you saved in disk access.
> [snip]
> 
> It's also not always this simple ... if you have a single threaded
> workload that doesn't overlap CPU and disk well, (de)compression may
> be free even if you're still CPU bound a lot as the compression is
> using cpu cycles which would have been otherwise idle..

Isn't that implied, though -- if the CPU is not busy (run top under a 
2.6 kernel and you'll see an IO-Wait number), then the first condition 
isn't satisfied -- CPU is not busy, disk is not idle.

But speaking of single threadedness, more and more desktops are shipping 
with ridiculously more power than people need.  Even a gamer really 
won't benefit that much from having a dual-core system, because 
multithreading is hard, and games haven't been doing it properly.  John 
Carmack is pretty much the only superstar programmer in video games, and 
after his first fairly massive attempt to make Quake 3 have two threads 
(since he'd just gotten a dual-core machine to play with) actually 
resulted in the game running some 30-40% slower than it did with a 
single thread.

So, for the desktop, compression makes perfect sense.  We don't have 
massive amounts of RAID.  If we have newer machines, there's a good 
chance we'll have one CPU sitting mostly idle while playing games. 
Short of gaming, there are few desktop applications that will fully 
utilize even one reasonably fast CPU.  The reason gamers buy dual-core 
systems is they're getting cheap enough to be worth it, and that one 
core sitting idle is a perfect place to do OS/system work not related to 
the game -- antivirus, automatic update checks, the inevitable 
background processes leeching a couple few % off your available CPU.

So for the typical new desktop with about 2 ghz of 64-bit processor 
sitting idle, compression is essentially free.

  reply	other threads:[~2006-08-29 19:11 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-27  0:34 Reiser4 und LZO compression Alexey Dobriyan
2006-08-27  8:04 ` Andrew Morton
2006-08-27  8:49   ` Ray Lee
2006-08-27  9:42   ` David Masover
2006-08-28 17:34     ` Jindrich Makovicka
2006-08-28 18:05       ` Edward Shishkin
2006-08-28 12:42   ` Jörn Engel
2006-08-29 13:14   ` PFC
2006-08-29 17:38     ` David Masover
2006-08-28 17:06 ` Hans Reiser
2006-08-28 17:37   ` Stefan Traby
2006-08-28 18:15     ` Edward Shishkin
2006-08-28 21:48       ` Nigel Cunningham
2006-08-28 23:32         ` Hans Reiser
2006-08-29  4:05         ` Jan Engelhardt
2006-08-29  5:41           ` Nigel Cunningham
2006-08-29  8:23             ` David Masover
2006-08-29  9:57               ` Nigel Cunningham
2006-08-29 11:09                 ` Ray Lee
2006-08-29 11:38                 ` Edward Shishkin
2006-08-29 22:03                   ` Nigel Cunningham
2006-08-29  4:59         ` Paul Mundt
2006-08-29  5:47           ` Nigel Cunningham
2006-08-29 13:45           ` PFC
2006-08-29 14:38             ` Stefan Traby
2006-08-29 15:55               ` PFC
2006-08-29 17:56                 ` Hans Reiser
2006-08-29 18:31                   ` David Masover
2006-08-29 18:36                     ` Gregory Maxwell
2006-08-29 19:11                       ` David Masover [this message]
2006-08-29 19:38                         ` Hans Reiser
2006-08-29 20:03                           ` David Masover
2006-08-29 22:15                             ` Toby Thain
2006-08-29 22:42                               ` David Masover
2006-08-30  9:17                                 ` PFC
2006-08-30 10:45                                   ` David Masover
2006-08-30 16:50                                   ` Edward Shishkin
2006-08-30 16:55                                     ` Hans Reiser
2006-08-31  9:32                                       ` Clemens Eisserer
2006-08-31 12:00                                         ` Edward Shishkin
2006-08-31 15:14                                           ` Clemens Eisserer
2006-08-31 16:55                                           ` Hans Reiser
2006-08-31 18:08                                             ` Edward Shishkin
2006-08-31 19:22                                         ` David Masover
2006-08-29 15:41             ` Gregory Maxwell
2006-08-29 17:42             ` Hans Reiser
2006-08-29  9:29         ` Edward Shishkin

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=44F4914A.1010005@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=gmaxwell@gmail.com \
    --cc=lists@peufeu.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.