|
KWSN Orbiting Fortress KWSN Distributed Computing Teams forum
|
View previous topic :: View next topic |
Author |
Message |
bryan[RS] Squire
Joined: 21 Dec 2005 Posts: 9 Location: Ohio, USA
|
Posted: Tue Feb 14, 2006 11:07 am Post subject: RieselSieve Client Problems |
|
|
Quote: | Hey, this probablly should be in the Help Section but since this thread is open. Has anyone had an issue where at first your system is doing well on the shrubs. Taking 4 to 5 hours to finish. System was rebooted. Then the system takes 9 to 10 hours to finish a shrub. I have looked in TaskManager and nothing else of consequences is running. LLR is at 99%. |
There is actually nothing wrong with your client (I think, by preliminary guess). Could you tell me what the specs of your rig are? The program has boundaries, called FFT's. Each time an FFT is crossed, the time to complete a "shrub" essentially doubles. This is not a flaw or an error, but how the math works. Right now, we are on the boundary of another FFT, so some shrubs will take twice as long as the shrub assigned before it or after it. One thing to check - if the K of the shrub (the first number before the *2 in the client output) is greater than 350000 or so, that's definitely your issue, no problems to check. If it's happening on lower k's, let me know the specs, what OS you're running, and the last 20 lines or so of your lresults.txt file to check.
HTH,
Bryan[/quote] _________________ Bryan
Stats Administrator
RieselSieve Project |
|
Back to top |
|
|
Lady DC Princess DC
Joined: 24 May 2002 Posts: 2516 Location: Hotlanta, Ga
|
Posted: Tue Feb 14, 2006 4:49 pm Post subject: |
|
|
Many thanks Bryan.
Just to start off, I am PC illiterate so if I have not answered all your questions please let me know what you need. I am running on a Windows XP Home Edition Version 2002 Service Pack 1. The hardware is a Hewlett-Packard Pavilion with an Intel Pentium. 4 CPU 40 GHz(Curiousity question - Does that mean that I can do what Grizz is trying to do?) . It is a 2.39 GHz with 512 MB of RAM.
If I understood the K question, it is 40597*2^2073285-1. So the k is 40597 (I think.)
The results for lresults.txt is:
Result 368411/2068706 succesfully sent to the server.
65531*2^2069070-1 is not prime. Res64: 4A01397FDC7C596D Time : 20211.293 sec.
Result 65531/2069070 succesfully sent to the server.
344759*2^2069416-1 is not prime. Res64: 840696873A549AEC Time : 68975.966 sec.
Result 344759/2069416 succesfully sent to the server.
344759*2^2070600-1 is not prime. Res64: A88B934F0D411C93 Time : 30481.977 sec.
Result 344759/2070600 succesfully sent to the server.
38473*2^2071163-1 is not prime. Res64: 164C3B0982EA84FB Time : 4850.779 sec.
Result 38473/2071163 succesfully sent to the server.
Iteration 1973203 / 2071812
273809*2^2071812-1 is not prime. Res64: A2520D056DDC776B Time : 1823.303 sec.
Result 273809/2071812 succesfully sent to the server.
275293*2^2072531-1 is not prime. Res64: D01060ED401F9B78 Time : 29586.011 sec.
Result 275293/2072531 succesfully sent to the server. _________________ |----Ni---Ni----|
Goddess of Spankings.
Leon Day is coming. A most wonderful day to celebrate.
[img]http://www.katrinashome.com/ladydc_counter.php[/img]
|
|
Back to top |
|
|
bryan[RS] Squire
Joined: 21 Dec 2005 Posts: 9 Location: Ohio, USA
|
Posted: Tue Feb 14, 2006 10:26 pm Post subject: |
|
|
Looking at those times, they are quite a bit longer than they should be. The ones that are extremely short (1800-5000 seconds) are tests that were finished after a reboot. But, the 69000 second test should not have taken that long unless:
1) Do you have any other DC clients running on the PC?
2) When is your weekly scheduled virus scan, adware/spyware sweep, defragmentation, windows update, or other scheduled maintenance?
3) Is this computer used for gaming, video/picture editing, or other intense applications?
To answer your questions-
Yes, the k was 40597. You have a Pentium 4, so no, you can't do what Grizz is trying to do. He has what appears to the program as 4 processors. What intrigues me is that you say you have a 40 GHz. Is it a 4.0? Because you also say it is 2.39 GHz. I have a 2.8 that takes 4 hours, 45 minutes a test (just about), so you should run 5 hr 15 min - 5 hr 30 mins. But 18-19 hours is waaaay too long. Pull up task manager (ALT-CTL-DEL) and let me know if llrnet.exe is getting 95-99% of the CPU, or if it is having to share. That will help a lot in determining the slowdown.
Bryan _________________ Bryan
Stats Administrator
RieselSieve Project |
|
Back to top |
|
|
Lady DC Princess DC
Joined: 24 May 2002 Posts: 2516 Location: Hotlanta, Ga
|
Posted: Wed Feb 15, 2006 12:50 am Post subject: |
|
|
bryan[RS] wrote: |
1) Do you have any other DC clients running on the PC?
2) When is your weekly scheduled virus scan, adware/spyware sweep, defragmentation, windows update, or other scheduled maintenance?
3) Is this computer used for gaming, video/picture editing, or other intense applications?
To answer your questions-
What intrigues me is that you say you have a 40 GHz. Is it a 4.0? Because you also say it is 2.39 GHz. I have a 2.8 that takes 4 hours, 45 minutes a test (just about), so you should run 5 hr 15 min - 5 hr 30 mins. But 18-19 hours is waaaay too long. Pull up task manager (ALT-CTL-DEL) and let me know if llrnet.exe is getting 95-99% of the CPU, or if it is having to share. That will help a lot in determining the slowdown.
Bryan |
Answers:
1. No other DC clients are running at this time. I use to have FAH running but I have decided that is on hold.
2. scheduled virus scan (manual), adware/spyware sweep, (manual for Lavasoft Ad-ware and Spybot S&D -I ran that yesterday, microsoft antispyware beta1 runs at 2:00 am every morning though.) defragmentation (manual), windows update (manual - in fact, it is waiting for me to manually do that) , or other scheduled maintenance (none)?
3. This is computer is used for email, google talk, and some web research sometimes. Also, I will run mIRC on it but it is not running now.
Oops, I missed a 2. there. It is 2.40 GHz. I went into System in the Control panel to read all of this.
llrnet.exe is running between 98 to 99% for the most part.
Many thanks for responding so quickly. _________________ |----Ni---Ni----|
Goddess of Spankings.
Leon Day is coming. A most wonderful day to celebrate.
[img]http://www.katrinashome.com/ladydc_counter.php[/img]
|
|
Back to top |
|
|
Cohiba Prince
Joined: 13 Jul 2004 Posts: 1721 Location: A tabbaco plantation
|
Posted: Wed Feb 15, 2006 9:10 am Post subject: |
|
|
P4 depending on age is notorious for slowing down over time. Called throttle clocking, when the cpu starts to over heat. Some P4's never will run 100% 24/7 due to this flaw, they will heat up and start throttling back. Two ways to fix this get a machine with a AMD processor, Clean out your computer and heat sink with canned air, can help sometimes cpu heat sinks don't work to well with a a nice dust bunny living in them. Make sure computer case is well ventalated, not stuck in the nice cubby hole of a fancy particle board computer desk. Most p4 throttling is not noticed untill it is compared against other p4's of same make, or performance takes a noticible hit.
Also this feature is nice that should your heat sink ever fall off, or fan stop working your cpu won't do a china syndrom on your motherboard. Meaning, it won't burn up, and melt the board or the cpu, unlike an AMD, but should you do distributed computing projects with a stock cooling fan and heat sink, you will eventually have degraded performance. _________________ Smoke-em if you got-em I do.. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|