Zhang Weiwu wrote:
> I tried to compare my Ultra 5 (1x333MHz CPU / ATA66 IDE / 256 MB )
> with Celeron 600 MHz box ( ATA 66, 256MB memory). My test is to 
> calculate the complecity of Linux kernel code.
> (command line: # sloccount /usr/src/linux-sparc-2.4.27/ )
> 
> On U5 it takes 325 seconds, on Celeron it takes 257 seconds.
> They both take almost same amount of kernel time, but U5 takes
> 210 seconds user time, while Celeron only takes 76 seconds.
> 

Here's my machine specs:

Ultra 2 Enterprise
2x300mHz CPU
1GiB Ram
2x18.1G SCSI drives (SUN18G's)
Kernel 2.6.6

Now, this is while running firefox, bittorrent (73KiB / 76KiB), xfce,
and about 9 xterm consoles.

Gotta love bittorrent for transferring ISO images. fwee!

Anywho:

(freshly emerged version:)
# time sloccount /usr/src/linux-2.4.28-sparc
[...]
real: 6m18.755s
user: 3m28.700s
sys:  1m40.590s

What this translates into? Eh. I dunno.  But my sparc is fast enough 
and stable enough for my at-work-workstation, and it's directly connected
to the internet 24x7 without any firewalls.  I can pretty much guarantee
that while it may have had hacks thrown at it, it's not going to respond
to any of the shell code that's out there. 

Oh, I guess I should state that sloccount isn't marked for ~sparc, but
compiles and works perfectly.  Dunno if somebody wants to tag it. :-)


--
Leif Sawyer   --  Pi@4398680
(907) 868-0116  ||  lsawyer@...  ||  leif@...  ||  internic: LS2540 
Network & Security Engineer -- General Communication Inc.
Alaskan Actor: http://home.gci.net/~leif
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT d+ s: a C+++(++)$ US++++$ UL++++$ P+++ L++(+++) E---
W+++ N+ o+ K w O- M- V PS+ PE Y+ PGP(+) t+@ 5- X R- tv b++(+++)
DI++++ D++ G+ e(+)* h-- r++ y+ PP++++ HH++++ A19 NT{--}
------END GEEK CODE BLOCK------
Decode it! http://www.ebb.org/ungeek/