What's new
By:
Guest viewing limit reached
  • You have reached the maximum number of guest views allowed
  • Please register below to remove this limitation
  • Already a member? Click here to login

Strange side effect of system migration

D

Diesel

Peak Forum Legend
PF Member
Messages
6,612
Highlights
0
Reaction score
1
Points
0
Peak Coin
0.000000¢
DB Transfer
0.000000¢
Since I migrated my old system into my new one, I noticed something quite strange.

Some background:
I had P3 600e@840 on an Asus P3B-F w/512MB Crucial PC133 CAS3.
The new system is a T-bird 800 on an Abit KT7-RAID w/640MB Crucial PC133 CAS3.

What I did was remove my 3 SCSI CD drives from the P3 and put them onto an identical SCSI card in the Athlon machine. I also moved the sound card (SB Live! Value) and the 512MB RAM from the P3->Athlon.

In place of the 512MB in the P3, I put in 128MB PC133 CAS2.
Basically, the P3 is the same as it was, but with 1/4 the RAM, no sound card, and 3 few SCSI devices.

Before the migration, my SETI@home work units took about 12-14 hours to complete.
Following the migration, the work units in the P3 now take a hair over 9 hours.
In both situations, these are work units that are left running on the machine with nothing else running. No settings have changed other than the removal of said equipment.

Can anyone think of a reasonable explanation as to why removal of a sound card and 3 SCSI devices would cause that significant a performance boost, especially considering that there's 1/4 the RAM in the system?

I'm stumped, but I'm not complaining.
smile.gif




------------------
"It's always funny until someone gets hurt, and then it's just hilarious."
 
Off the top of my head.. Different SETI blocks take different amounts of time.. maybe you got lucky and got a string of them that were smaller.. 12-14hrs on a P3 system seems way too long anyways.. my Celeron 333 ran a block in about the same time period (on avg)...
 
WaterB> This is on every block since (about 10). One last night took 9:10.
I don't think I just got a lucky string that long. And wouldn't the systems running at work and on my laptop see the same benefit if shorter work units were being passed around.

My fresh Athlon system is taking roughly 12 hours.
My experience has been that they take about 10-14 hours on a P3-class machine.
The P3 733's we have at work take that long, my P3 450 laptop takes about 10 hours running the CLI client, which is supposed to be much faster.


------------------
"It's always funny until someone gets hurt, and then it's just hilarious."
 
Last night, work unit got done in 7 hrs 11 min.
I don't know what I did to that machine.
smile.gif



------------------
"It's always funny until someone gets hurt, and then it's just hilarious."
 
You must log in or register to reply here.
Back
Top