Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Desktops (Apple) Businesses Software Technology (Apple) Apple Hardware Linux Technology

Gentoo is Fast on New G5s 119

Durin_Deathless writes "According to a thread on the Gentoo/PPC forums, some Gentoo users have installed Gentoo on their new G5s without any problems whatsoever. Benchmarks are extraordinary: compiling kde on a G5 running at half speed takes 15 minutes, while it takes one hour on the fastest P4 available. Gentoo/PowerPC lead, Pieter Van den Abeele, reported that the machine currently runs at half speed due to fan controlling hardware not yet supported. The Gentoo team will post benchmarks, and will update installation instructions as soon as possible. There is some question as to what exactly was compiled, as the times seem impossibly fast even on the P4."
This discussion has been archived. No new comments can be posted.

Gentoo is Fast on New G5s

Comments Filter:
  • compiling KDE (Score:5, Informative)

    by platipusrc ( 595850 ) <erchambers@gmail.com> on Wednesday September 10, 2003 @12:28AM (#6918237) Homepage
    There was a followup post where the originator of the thread stated that he actually only compiled KDEBASE and KDELIBS...not the entire KDE setup. So no, unfortunately the G5s don't bring us 10x the performance just yet :)
  • Comment removed (Score:5, Informative)

    by account_deleted ( 4530225 ) * on Wednesday September 10, 2003 @12:37AM (#6918300)
    Comment removed based on user account deletion
  • The real test. (Score:3, Informative)

    by BrookHarty ( 9119 ) on Wednesday September 10, 2003 @12:42AM (#6918330) Journal
    KDE might be nice, but try compiling Mozilla with all options, email/irc/etc... Thats what I'd like to see as a benchmark test.
  • What he compiled... (Score:4, Informative)

    by Lally Singh ( 3427 ) on Wednesday September 10, 2003 @01:25AM (#6918561) Journal
    kdebase & kdelibs.
  • Re:compile time? (Score:4, Informative)

    by Arielholic ( 196983 ) on Wednesday September 10, 2003 @06:59AM (#6919582)
    You can't even download all the KDE packages in 15 minutes

    If you would have read the thread, you would have known that it took him 3 hours to download kde.
  • Bullshit (Score:2, Informative)

    by Anonymous Coward on Wednesday September 10, 2003 @09:04AM (#6920268)
    This guy is a liar. Look through some of his posting history. He claimed to have downloaded America's Army source, compiled and run it on Linux/PPC.
  • About twice as fast. (Score:4, Informative)

    by jhesse ( 138516 ) on Wednesday September 10, 2003 @10:34AM (#6921070) Homepage
    ...at least when running the spiffo graphics. (for some reason, the mac used *much* less cpu for that)

    They were about neck-and-neck without the spiffo graphics, although the mac seemed slightly faster.
    (Hard to tell, since they were different clockspeeds *and*
    datasets.) Averages here...

    This is on P2 and P3 chips. The Celerons were 3-5 times slower because it couldn't keep the data in cache.

    Keep in mind that Seti@Home doesn't use Altivec or MMX.
  • by ComputerSlicer23 ( 516509 ) on Wednesday September 10, 2003 @02:11PM (#6923175)
    I'll point out that's not possible.... :-)

    That problem at that point was that the people who where writting the code you ran under DOS we're stupid. The OS got out of your way. Other then the possibility of the filesystem was slower, DOS should have ran faster. Possibly only mildly faster, but faster.

    Linux could multi-task, which means there is a scheduler. The scheduler is pure overhead in terms of speed. So now you are down to comparing apps to apps. Maybe a little bit of filesystem thrown in for giggles. I supposed DOS could have had a crappy timer interrupt or something, or crappy serial I/O interrupts. However, as I recall, most of the actual O/S of DOS was really in the BIOS, so blame the MoBo maker. The BIOS implemented all of the functionality to talk with hardware so DOS didn't have to write any real drivers.

    As far as Linus not being a C programmer, go read his biographies and the early days of Linux. Go read interviews with his old roommate. He wasn't a C programmer. He originally started doing it in assembly. In fact the whole project was to learn more about the x86 assembly, it started as a terminal emulator.

    He didn't know how sprintf worked. His roommate Lars implemented the original sprintf for the kernel for him.

    Kirby

  • by Anonymous Coward on Wednesday September 10, 2003 @03:01PM (#6923656)
    Let's analyze this article:

    some Gentoo users have installed Gentoo on their new G5s without any problems whatsoever.

    No. Only one entirely unreliable user made outrageous claims including running Gentoo. Not users but user.

    while it takes one hour on the fastest P4 available.

    The user said "my Pentium 4" without saying anything about what that Pentium 4 was. For all we know it could be an old 1.6Mhz with 128MB.

    Pieter Van den Abeele, reported that the machine currently runs at half speed due to fan controlling hardware not yet supported.

    He says that it may be possible to get the kernel working and if it did then it would run at half-speed. There is no "machine currently" running it to confirm this and it also proves that the other guy is lying.

    The Gentoo team will post benchmarks, and will update installation instructions as soon as possible.

    According to Abeele - "As far as I know, *none* of the Gentoo developers that are working on support for the G5." Now I guess that eventually they will benchmark and update installation instructions but it is obviously not on the radar screen right now.

    The author of this article and pudge should be whipped for putting this awful article up.
  • by ComputerSlicer23 ( 516509 ) on Thursday September 11, 2003 @03:39PM (#6935142)
    Uhhh, do you know anything about the guts of DOS? DOS really doesn't do anything. DOS isn't an OS in the technical sense. It's a boot loader, and let's you provide access to BIOS routines. It wasn't DOS that was slow. It was the BIOS routines.

    That's why Windows 3.11 could run on it. It's why DOS Extenders ran on it. DOS didn't *DO* anything other then command.com really, and a little bit of filesystem stuff. Once you started running DOS you pretty much had complete control of the hardware. The BIOS did most of the heavy lifting on serial I/O, writing to the screen, reading or writing from the floppy or harddrive. That's why the BIOS had to be reversed engineered before you could make another PC run DOS. The BIOS did all the work. It's also why DOS ran a load more hardware then Linux did (at the time).

    You go get a copy of DOS, go get a copy of an old Linux 0.2 kernel. Fire up program that calculates primes. Neither one of them is particularly faster or slower then the other, assuming you used similar compilers. Do that again with Windows, and you'll probably find that Windows runs about 2-5% slower (last time I checked), due to context switching speed and generic overhead of the (GUI updates, and other subsystems you don't have to have on a Linux machine).

    Kirby

A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson

Working...