Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: F@H vs S@H: Benchmarks




  1. #11
    Join Date
    Aug 2003
    Posts
    65

    Default

    Quote Originally Posted by minibubba

    *btw, to the guys with the power... I wouldn't mind seeing something like this on the front page to stir up some intrest in the TT DC teams ;)
    Iv noticed most of the top teams have a link on the main web site front page. Also they put folding rite where you can see it on the main forum page, in DC forums or web Teams. I had to search to find the DC forums here. The people that run this site have the power to make our folding team a powerhouse...

  2. #12
    Join Date
    Jul 2002
    Posts
    662

    Default

    Quote Originally Posted by Fatguy3
    ... I had participated in SETI@Home in the past...
    Are those Units parked in any meaningful location? Hint. Hint. ;)

    Nice bit of analytical work Fatguy3. :thumb:

    I do have some questions, however. I'm wondering how much progress was made on the F@h or S@h units during the benching/gaming vs the same length of time while running the DC program by itself? I suspect that the wu processing suffered at the expense of the benching/gaming.

    I am not at all familiar with the F@h programs (GUI or CLI), however, there are three priority settings in SETI Driver for running the command line version of S@h. They are 'High,' 'Normal' and 'Low.' What setting was used while benching with S@h running and what setting corresponds to the F@h setting? Or does the CLI version of F@h operate like the typical settings for the GUI version of S@h and back off completely while there are other processes with higher prioity running?
    :-(

  3. Default

    I only had it installed for about a week, on a P3 500. So even If I could remember my username, it wouldnt be worth while anyway
    The FatGuy's Rig:

    <small>AMD 1600+ XP O/C'd to 1560 mhz // Thermaltake Volcano 7+ // Aopen AK77 Pro K266(A) Chipset O/C'd to 147 mhz // 256MB Elixir PC2100 DDR CAS2 // Visiontek GeForce4 Ti4200 O/C'd to 310/580 w/ Thermaltake HSU // SoundBlaster Audigy X-Gamer // WD205BA 20GB 7200 // Sony 52x/24x/52x // Linksys 10/100 NIC // ThermalTake 480w Butterfly PSU // Silver Windowed Aluminum Mid-Tower Case (Modded) // Vantec Nexus Fan Controller// Thermaltake 80mm Blower // 3xEvercool 80mm Fans // 2xBlue Cold Cathodes // 2xSound activated Blue Cold Cathodes // Dell 17" Monitor // Microsoft Trackball // Creative 5.1 Speakers</small>

    Come Crunch with TweakTown

    <img src="http://www.statgfx.com/statgfx/folding/?&username=FatGuy3&border=0,0,0&custom =0,0,255&label=0,0,0&header=255,0,0&st ats=0,0,255&trans=yes&template=fah_origina l&.jpg" alt="www.Statgfx.com" />

  4. #14
    Join Date
    Jul 2002
    Posts
    662

    Default

    Quote Originally Posted by Fatguy3
    I only had it installed for about a week, on a P3 500. So even If I could remember my username, it wouldnt be worth while anyway
    Ok, thanks. BTW I've added some questions to my previous post.
    :-(

  5. Default

    #1 Although I did not record the times of units processed, performance defintely suffered during gameplay. This is to be expected, as @Home only eats up your idle processes. This was more of a test of Microsoft's CPU Priority Coding then anything really.

    #2 Both progs were run in command line mode with the process set at lowest setting, Idle for F@H and Low for S@H. Im sure if I upped the priority it would result in performance loss.

    Thanks for the questions though. I may do some tests to see how long a certain frame takes without any progs running vs Gaming vs Sandra BurnIn Test (That would be a killer) But it really wouldnt prove anything that we didnt know. Oh well, perhaps sometime today. :)
    The FatGuy's Rig:

    <small>AMD 1600+ XP O/C'd to 1560 mhz // Thermaltake Volcano 7+ // Aopen AK77 Pro K266(A) Chipset O/C'd to 147 mhz // 256MB Elixir PC2100 DDR CAS2 // Visiontek GeForce4 Ti4200 O/C'd to 310/580 w/ Thermaltake HSU // SoundBlaster Audigy X-Gamer // WD205BA 20GB 7200 // Sony 52x/24x/52x // Linksys 10/100 NIC // ThermalTake 480w Butterfly PSU // Silver Windowed Aluminum Mid-Tower Case (Modded) // Vantec Nexus Fan Controller// Thermaltake 80mm Blower // 3xEvercool 80mm Fans // 2xBlue Cold Cathodes // 2xSound activated Blue Cold Cathodes // Dell 17" Monitor // Microsoft Trackball // Creative 5.1 Speakers</small>

    Come Crunch with TweakTown

    <img src="http://www.statgfx.com/statgfx/folding/?&username=FatGuy3&border=0,0,0&custom =0,0,255&label=0,0,0&header=255,0,0&st ats=0,0,255&trans=yes&template=fah_origina l&.jpg" alt="www.Statgfx.com" />

  6. #16
    Join Date
    Feb 2003
    Location
    Fincastle, IN, USA
    Posts
    3,776

  7. Default

    Danke, I just found my Works Suite 99 Disk (Super Ghetto Version) and I'm gonna draw up some sweet ass graphs and shizat, ya know, for the ladies :devil:
    The FatGuy's Rig:

    <small>AMD 1600+ XP O/C'd to 1560 mhz // Thermaltake Volcano 7+ // Aopen AK77 Pro K266(A) Chipset O/C'd to 147 mhz // 256MB Elixir PC2100 DDR CAS2 // Visiontek GeForce4 Ti4200 O/C'd to 310/580 w/ Thermaltake HSU // SoundBlaster Audigy X-Gamer // WD205BA 20GB 7200 // Sony 52x/24x/52x // Linksys 10/100 NIC // ThermalTake 480w Butterfly PSU // Silver Windowed Aluminum Mid-Tower Case (Modded) // Vantec Nexus Fan Controller// Thermaltake 80mm Blower // 3xEvercool 80mm Fans // 2xBlue Cold Cathodes // 2xSound activated Blue Cold Cathodes // Dell 17" Monitor // Microsoft Trackball // Creative 5.1 Speakers</small>

    Come Crunch with TweakTown

    <img src="http://www.statgfx.com/statgfx/folding/?&username=FatGuy3&border=0,0,0&custom =0,0,255&label=0,0,0&header=255,0,0&st ats=0,0,255&trans=yes&template=fah_origina l&.jpg" alt="www.Statgfx.com" />

  8. #18
    Join Date
    Nov 2001
    Location
    New England Highlands, Australia
    Posts
    21,907

    Default

    Quote Originally Posted by Fatguy3
    Danke, I just found my Works Suite 99 Disk (Super Ghetto Version) and I'm gonna draw up some sweet ass graphs and shizat, ya know, for the ladies :devil:
    So what happened with those graphs? :?:

  9. #19
    Join Date
    Dec 2002
    Posts
    4,246

    Default

    there's a very in-depth anyalsis of f@H and system performace here: http://www.tech-report.com/etc/2002q...t/index.x?pg=1

    and it even includes graphs :)

    here's the conclusion for those of you too lazy to follow the link and actually read it:
    [b]The results of our testing couldn't be clearer, at least for the systems we've tested today. Quite simply, the impact of running Folding@Home in the background is negligible. Even the most discerning users won't notice it. Windows allocates CPU time slices according to process priority, and as long as the Folding@Home client is running as an idle-priority task (which is how it runs by default), one shouldn't notice any slowdown. Remember that we're also running FireDaemon in the background, and the impact of this small service management tool is also negligible.

    With the results we've seen here, one more exuse for not donating excess CPU time to the Folding@Home project is gone. Whether you're playing games, encoding media files, surfing the web, slaving away in a cubicle at work, or mumbling to your computer, running the Folding@Home client won't slow you down. To effectively fold, however, you will need an always-on Internet connection. Also, expect to pay a few dollars a month extra on your electric bill as your system's CPU crunches away at full tilt all the time. In my book, those are small sacrifices, especially if you count completing a work unit as your good deed for the day.

    So why not head on over to Stanford's Folding@Home page and download the client?
    seem right on par with what Fatguy3 has already told us :)
    I've gone too far and need to move on!

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •