Overclock.net - An Overclocking Community - Reply to Topic

Thread: Projects of the Month for December 2017 Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
01-01-2018 07:10 AM
tictoc

For sure.  I had a heck of a time getting any ATLAS work after they ramped up their production.

01-01-2018 06:56 AM
mmonnin Yeah the CERN team fired back up and zipped right past us. Seemed to be a lot of server space and upload issues when they came back.
01-01-2018 06:37 AM
tictoc

POTM Final Total

[email protected]

Start: 22 - Goal: 21 - End: 22 |  We did pass the team we were originally gunning for, so I'm declaring this goal achieved. :D

 

SRBase

Start: 36 - Goal: 30 - End: 26 |  We nearly made it in to the top 25.  Great job team. :thumb:

 

[email protected]

Start: 22 - Currently: 22 - End: 22 |  This was a pretty impossible goal. We were making up some ground before Team Russia saw us coming and turned up the juice, which is a win for the project. :D

 

 

Good job everyone. :cheers: 

 

Working on the January POTM, and they will be up shortly.

12-21-2017 03:33 AM
mmonnin Watch out for LHCb. Many people have issues with them running for 10min, condor not being able to communicate and then the task aborts. One computer does that for me, another is fine.
12-20-2017 10:03 PM
tictoc

I' m running 15 sixtrack tasks now.  I agree completely on the merits of the project. :)

 

The ATLAS tasks were running without too many issues, but when the ATLAS server went offline I started running the Theory and LHCb tasks.  I might go back to running just ATLAS and sixtrack.

12-20-2017 09:53 PM
emoga @tictoc I switched to sixtrack when atlas was having its uploading issues. It's much smoother on the network, as well as the hard drives.

That's the thing with LHC...it's one of the most important distributed computing projects out there (imo)...but it also demands the most ram, bandwidth and patience from its users. rolleyes.gif
12-20-2017 08:15 PM
tictoc

I'm currently clearing out my LHC queue.  The constant traffic back and forth to the LHC servers murders my lowly DSL connection.  I will probably keep one rig crunching one or two tasks, but running 10+ tasks at a time, is not something that I can keep doing without throtlling the heck out of the traffic to the LHC servers. 

 

If I am going to keep running LHC, I will probably need to set up a local cache server to minimize all of the http overhead that LHC has.

12-18-2017 06:47 PM
tictoc
Quote:
Originally Posted by tictoc View Post
 

The errors and lockups that I was having on Einstein on my 1070s and 290s were actually due to unstable memory. 

 

I was running my 1333 sticks at 1866, and apparently running that speed was not quite stable.  I caught the errors on SRBase, so I dropped the speed, and now my 290s have been crunching Einstein without issue for the last day and a half.:D

 

Quoting myself. :D

 

Evidently that was not the issue.  Not sure what it is, and I don't have time to mess with it right now, but still seeing odd lock-ups and driver crashes when I run Einstein.  I'm going to put a 480 back on Einstein, and the 290s are going back to MilkyWay for now.

12-15-2017 08:31 PM
Egilman
Code:
<app_config> 
    <app> 
        <name>hsgamma_FGRPB1G</name> 
            <gpu_versions> 
                <gpu_usage>0.33</gpu_usage>
                <cpu_usage>0.2</cpu_usage> 
            </gpu_versions> 
    </app> 
</app_config> 

this is the app_config I was running mine on.

yes 3x, start out at stock clocks as long as they are stable.....
Then adjust upwards as long as they remain stable..........
And from what I remember, doesn't need a lot of memory....

This put my machines in the top ten on the project in the dailies.
12-15-2017 07:47 AM
tictoc

The errors and lockups that I was having on Einstein on my 1070s and 290s were actually due to unstable memory. 

 

I was running my 1333 sticks at 1866, and apparently running that speed was not quite stable.  I caught the errors on SRBase, so I dropped the speed, and now my 290s have been crunching Einstein without issue for the last day and a half.:D

This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off