• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

My break with the Seti Cavalry

G

Green Man

Golden Member
The Celeron Scout Craft @ 550 which was Cracking RC5 for TA_SETI has been redeployed to the SETI front. The Scout Craft was cracking at about 1.5Mkeys/sec. I expect 13hour WUs from it.

Furthermore, an Athlon 750 gunship has been detached from my SETI fleet, and has been sent to perform advanced Scouting duties on the RC5 front. The gunship has been turning in 11hour WUs. It has just benchmarked RC5 at 2.65Mkeys/sec.

The gunship has not been attached to TA_SETI, but has been assigned a new task force identified which should show up on the screen in 24 hours.

There is no rift between the SETI CAVALRY and the SpookyFish subfleet, merely a reorganization to make maximum use of assets.😀

😉

 
I have a Celeron 366@ 550 with CAS2 RAM on a BX chipset running v3.03 CLi it does most WU's in 10.5hrs🙂.
(btw my fathers Athlon 700 with 133MHz CAS2 RAM does most WU's in 8.5hrs with v3.03 CLi)
 
Assimilator1

Looks like nice SETI times on both of those boxes. These two of mine get very heavy use, but I wonder what I could do to optimize them. I guess I should look at memory timings. I have them set by SPD on the Athlon box, I'll look to see if there is an option to set 4way interleave. On the Celeron, it's on a gigabyte BX board...a 6BXC I think. Any speed tips are welcome🙂
 
and here i thought we were guys on horses... at least, that was the image when i made up the name. ah well 😛
 
Spookyfish
(cool nick btw🙂)
The only tweak the Celeron has is the RAM is running at CAS2 ,that alone makes quite a difference.You could try that if your RAM can take it.

The Athlon(classic) has the following RAM settings.133MHz(HST CLK + PCI CLK),CAS2,4 way interleave & Turbo.That's on Crucial PC133 CL2 RAM.

Note that the text(CLi) version of SETI is considerabley faster than the GUI version ,it took about 2.5hrs off WU times on the Athlon🙂.

Elf
lol
 
Assimilator1 Thanks for the tip!
I had the Ram on the Athlon (SlotA KX133) at 133, but I also had it set to SPD, which wanted CAS3. That should give me a boost, but now that Athlon is doing RC5. As I understand it, RC5 is as reliant on memory speed. (I'm not sure I'm right about this)
The Celeron is already set to CAS2, so it should be all ready for maximum output. I'm using the CLI.
 
Assimilator1 is right. RC5 is not affected at all by memory timings, the amount of memory, the speed of the memory bus, or anything other than the speed of the CPU. The data that RC5 works with fits nicely inside the L1 cache of most processors, meaning that the CPU never has to resort to accessing data from main memory like it does with SETI.

It looks like a good switch, though. You doubled the RC5 speed while only losing an hour or two per SETI WU!! 😀

Nick
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top