• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Have you got pie today?

:peace:
 
Vinska said:
Assuming You have the distro-provided Boinc, open the /etc/boinc-client/cc_config.xml file as root. You should see something like:
Code: 
<!--
This is a minimal configuration file cc_config.xml of the BOINC core client.
For a complete list of all available options and logging flags and their
meaning see: http://boinc.berkeley.edu/trac/wiki/ClientMessages
-->
<cc_config>
  <log_flags>
    <task>1</task>
    <file_xfer>1</file_xfer>
    <sched_ops>1</sched_ops>
  </log_flags>
</cc_config>
disregard everything it holds and edit it into:
Code: 
<cc_config>
	<options>
		<report_results_immediately>1</report_results_immediately>
	</options>
</cc_config>
Save. Reload config file. Enjoy Your insta-reporting.
Click to expand...
I just figured it out. I knew I had to add the options/report line to the config file, I just had to figure which one and just how to add the line. But I got it added using terminal (sudoedit) and all is good. :toast:
 
Last edited:
Vinska said:
Assuming You have the distro-provided Boinc, open the /etc/boinc-client/cc_config.xml file as root. You should see something like:
Code: 
<!--
This is a minimal configuration file cc_config.xml of the BOINC core client.
For a complete list of all available options and logging flags and their
meaning see: http://boinc.berkeley.edu/trac/wiki/ClientMessages
-->
<cc_config>
  <log_flags>
    <task>1</task>
    <file_xfer>1</file_xfer>
    <sched_ops>1</sched_ops>
  </log_flags>
</cc_config>
disregard everything it holds and edit it into:
Code: 
<cc_config>
	<options>
		<report_results_immediately>1</report_results_immediately>
	</options>
</cc_config>
Save. Reload config file. Enjoy Your insta-reporting.



Also, [Ion], it appears here, SN2S cycles through high and low memory usage WUs. As You saw previously, those WUs were all running with ~450MB memory usage. While these use 43 to 72 MB:
http://img51.imageshack.us/img51/7223/76qu.png

Here, they cycle as a "herd" - either all high or all low memory using ones are running. Changes every half a day or so... *shrug*
Click to expand...

Awesome! I didn't know where the file was kept--now all is clear! :toast:

And that's interesting to see the change in memory usage over time--but I suppose that it means that all of our systems need to be prepared for the "worst-case" scenario (ie .5GB RAM/CPU thread).
 
[Ion] said:
but I suppose that it means that all of our systems need to be prepared for the "worst-case" scenario (ie .5GB RAM/CPU thread).
Click to expand...

I seem to remember someone else saying this a while back :p

The 8GB of ram in most of my rigs seems to help them crunch smoother/have better output than when they had 4GB
 
Norton said:
I seem to remember someone else saying this a while back :p

The 8GB of ram in most of my rigs seems to help them crunch smoother/have better output than when they had 4GB
Click to expand...

Ehh, I don't see a point for 8GB on them. I have 16GB in my gaming system, but otherwise, 4GB works fine on an i7 or FX8. That's what all of my i7 systems have and the 8350, and no difficulties arise (although they just run the OS + BOINC, so there's not a lot of overhead).

I can try poking around to see if doubling the RAM in the i7 helps any.

At least on the 4P setup, I've never seen RAM usage go over 9GB--and usually it hovers in the 4GB range. So, realistically, even 12GB RAM (vs the 32GB) would probably be fine...
 
My Ubuntu rig is now reporting results immediately!

Thanks to Mad Shot and Vinska for the helpful tips!!! :toast:-:respect:
 
Norton said:
I seem to remember someone else saying this a while back :p

The 8GB of ram in most of my rigs seems to help them crunch smoother/have better output than when they had 4GB
Click to expand...

I know you said that back on the GPU work...
 
Time for Pie.....! :)
September 2nd, 2013
Top10090213.jpg

Are you in our Top 20?
Top20090213.jpg

Top30090213.jpg
LOLcat week!!!.... :D
090213Lolcats.jpg


Congrats to All of our crunchers!!! :toast:
 
Good job again tonight! :toast: :rockout: :toast:
 
I can maybe see a benefit to instant reporting in the sense of.. more stable PPD? Anything I'm missing?
 
hopefully I can start to spice things up in the top 20 soon. Should be getting up to speed by tomorrow.
 
xvi said:
I can maybe see a benefit to instant reporting in the sense of.. more stable PPD? Anything I'm missing?
Click to expand...

Basically it becomes a pain in the ass because it seems now that Linux rigs don't want to report by themselves at all. When I was running the Ubuntu rigs before they would report by themselves, maybe not at the most opportune times but they would report once or twice a day. Now it seems they don't want to report at all and you have to manually report them. I'm not always available to report them when they need to be and I can have a stack of results sitting.
 
  • Like
Reactions: xvi
There could be something wrong with Your Boinc network setting, then.
 
Vinska said:
There could be something wrong with Your Boinc network setting, then.
Click to expand...

I think the issue is in the BOINC Manager basic settings when you install under Ubuntu. I had the same issue but the quick edit to the cc_config fixed it right up :toast:

iirc... the BOINC Manager was included with prior Ubuntu packages (prior to 12.04 LTS) so the base setting may have been setup to report properly from the start?
 
Vinska said:
There could be something wrong with Your Boinc network setting, then.
Click to expand...

Network setting are good. Also they are the default as installed. I noticed the change in mine with the new install of 13.04. With 12.10 I didn't have the issue but still wanted it to report immediately anyway. So it is set to where I wanted anyhoo. :toast:
 
Well, just got home and found my rig stuck on the BSOD screen, and apparently it has been like that for several days, since I've reported nothing in days. I left Saturday morning and Saturday I didn't make top 30, so it seems that for the last 4 days, my rig has been doing nothing; I should have left it off :shadedshu

Anyway, now it's running and I'll be running the 2nd rig most of tonight to try to make up for some loss :rockout:
 
Let's see if I can get in the top 20 again...
 
manofthem said:
Well, just got home and found my rig stuck on the BSOD screen, and apparently it has been like that for several days, since I've reported nothing in days. I left Saturday morning and Saturday I didn't make top 30, so it seems that for the last 4 days, my rig has been doing nothing; I should have left it off :shadedshu

Anyway, now it's running and I'll be running the 2nd rig most of tonight to try to make up for some loss :rockout:
Click to expand...

Well that sucks! Was it acting unstable before you left?
 
[Ion] said:
Well that sucks! Was it acting unstable before you left?
Click to expand...

Not really, no. The only time I ever really have any issues with my pc is while playing FC3; that game has given me grief since day 1. But for crunching, it has been completely stable, never a BSOD from WCG.

I restarted when I got home, and since then everything has been perfectly fine. Let's hope the issues are gone! :rolleyes:
 
manofthem said:
Not really, no. The only time I ever really have any issues with my pc is while playing FC3; that game has given me grief since day 1. But for crunching, it has been completely stable, never a BSOD from WCG.

I restarted when I got home, and since then everything has been perfectly fine. Let's hope the issues are gone! :rolleyes:
Click to expand...

Huh. That's odd. I'd expect that it should at least have displayed instability issues before--but apparently not!

Perhaps time to back off the OC a bit?
 
[Ion] said:
Huh. That's odd. I'd expect that it should at least have displayed instability issues before--but apparently not!

Perhaps time to back off the OC a bit?
Click to expand...

I'd hate to but if issues persist, then yeah I may well have to. I'll be letting it run and I'll be looking for any issues.

And if issues do persist, I'll drop the OC slightly. If that does it, I guess degradation does happen. :laugh:
 
Time for Pie.....! :)
September 3rd, 2013
Top10090313.jpg

Are you in our Top 20?
Top20090313.jpg

Top30090313.jpg
LOLcat week!!!.... :D
090313ikealolcat.jpg


Congrats to All of our crunchers!!! :toast:
 
Time for Pie.....! :)
September 4th, 2013
Top10090413.jpg

Are you in our Top 20?
Top20090413.jpg

Top30090413.jpg
LOLcat week!!!.... :D
*Today's cat submitted by t_ski :toast:
090413lolcatltdan.jpg


Congrats to All of our crunchers!!! :toast:
 
Well, good news: my rig has been running fine and I'm slowly climbing back up; I hope to be back around #18 tomorrow. :)
Great work team :toast:
 
How I foresee pie in the future.
Pie.png
 
You must log in or register to reply here.
Back
Top