MMM
Results 1 to 25 of 595

Thread: The Linux Help and Tutorial Thread

Hybrid View

  1. #1
    Xtreme Legend
    Join Date
    Mar 2008
    Location
    Plymouth (UK)
    Posts
    5,279
    Not seeing criticism but we are possibly talking at crossed purposes.

    When I am talking about seeing 94% I am referring to the Boinctasks screen which, oddly enough, I am tending to go with because it seems to accurately fit with the amount of lost time (the difference between real time and cpu time for a wu.)

    All the while there is 94% showing in Boinctasks there is 100% showing on all bar one thread (98%) in top.

    When I was referring to the idle time, that was seen in the info across the top of top: user, system, nice, idle, wait etc.

    All together this is saying to me that if it is not the OS being inefficient, seemingly the case judging by the 100% for each thread showing but there is only 6% of idle time when running 15 threads then the losses must lay elsewhere and perhaps a new install would rule out less than optimum "drivers" etc.

    It could be lesser hardware causing this but....

    I am just following my nose on this and my logic may be faulty too bearing in mind my lack of detailed knowledge on how this stuff actually works..... but it should only cost an hour to find out.

    EDIT: I have an issue trying to get a screenshot... what I get just now is a screen that is older than the current screen. any tips on that and I will gladly post.

    I changed my value using boinktasks> extra> edit config file> <no_priority_change>1</no_priority_change>

    I tried just getting it to read the config file again but had to actually re-start boinc for it to work

    You could do this with gedit and just add the above line to cc_config. (listen to me talking to the bearded one ....)
    Last edited by OldChap; 11-12-2013 at 04:21 PM.


    My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.
    79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!

  2. #2
    Xtreme Member
    Join Date
    Oct 2012
    Posts
    448
    I was wondering if any of you Linux guys who have switched over to the newest BOINC client for 64 bit Linux (7.2.28?) have seen a difference in crunching times as compared to 7.0.65 or .64?


    Also, as a Linux newb, I am still learning things about the OS. To that end, did you or do you have to use a command line way of updating to the new version or did you have to uninstall the current BOINC client and then install the new one?
    Last edited by yojimbo197; 11-12-2013 at 04:27 PM.
    Desktop rigs:
    Oysterhead- Intel i5-2320 CPU@3.0Ghz, Zalman 9500AT2, 8Gb Patriot 1333Mhz DDR3 RAM, 120Gb Kingston V200+ SSD, 1Tb Seagate HD, Linux Mint 17 Cinnamon 64 bit, LG 330W PSU

    Flying Frog Brigade-Intel Xeon W3520@2.66Ghz, 6Gb Hynix 1066Mhz DDR3 RAM, 640Gb Hitachi HD, 512Mb GDDR5 AMD HD4870, Mac OSX 10.6.8/Linux Mint 14 Cinnamon dual boot

    Laptop:
    Colonel Claypool-Intel T6600 Core 2 Duo, 4Gb 1066Mhz DDR3 RAM, 1Gb GDDR3 Nvidia 230M,240Gb Edge SATA6 SSD, Windows 7 Home 64 bit




  3. #3
    Xtreme Cruncher
    Join Date
    Jan 2009
    Location
    Nashville
    Posts
    4,162
    Quote Originally Posted by yojimbo197 View Post
    I was wondering if any of you Linux guys who have switched over to the newest BOINC client for 64 bit Linux (7.2.28?) have seen a difference in crunching times as compared to 7.0.65 or .64?


    Also, as a Linux newb, I am still learning things about the OS. To that end, did you or do you have to use a command line way of updating to the new version or did you have to uninstall the current BOINC client and then install the new one?
    I have seen no difference but the newer one allows you to use app_config.xml

    see this thread on how to update and or install newest Boinc.

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •