Distributed Compute Labs Support

Problems running DCC Miner on large core hosts

Comments

10 comments

  • Avatar
    MAYA

    Use the OPERA browser to solve the problem.

    1
    Comment actions Permalink
  • Avatar
    NickPar

    I wonder if using opera on a Windows 10 computer would actually be more efficient? I think I will try it and see if Chrome and Opera don't mind sharing the space.

    Would like to here from others how their experience goes.

    1
    Comment actions Permalink
  • Avatar
    NickPar

    Thanks CK-N. Good to know it works well.

    1
    Comment actions Permalink
  • Avatar
    Greg Agnew

    Can you give more information on your system?

    Chrome version? OS? CPU/RAM Memory? Swap space?

    We've been running a thread-ripper (32 cores, 64 threads) and 64gb RAM at 50 cores without issue. Whenever we've experienced a crash it was because we've run out of memory (on purpose for testing). The tasks in the scheduler right now should not be using up too much however.

    If you open your developer console you can set the number of workers. (UX on the way)

    compute.stopMining()

    then

    compute.defaultMaxWorkers = #  && compute.mine()
    or 
    compute.mine(# of cores)


    2
    Comment actions Permalink
  • Avatar
    NickPar

    Those commands are just what I needed, thanks Greg Agnew :D

    Now I can run some on my laptop while I work.

    1
    Comment actions Permalink
  • Avatar
    NickPar

    It seems it's safer to use the compute.defaultMaxWorkers = # and then the start/stop button on screen or you end up not stopping all task with compute.stopMining as I had to logout and back in to reset the running task to zero. Upon using compute.defaultMaxWorkers = # and the the start/stop button to run it the behavior was as expected.

    1
    Comment actions Permalink
  • Avatar
    CK-N

    I gave up on the non-working Chrome hosts and am using Opera instead.

    I will just highlight one machine, but the current problem is happening across hosts; freezing tasks at 100%.

    Host specification:

    • OS: Linux Mint 19 (x86_64; X-Cinnamon)
    • Browser: Opera version 57.0.3098.116
    • Memory: 24GB RAM (around 5GB being used when DCC miner is in use)
    • Swap Space: 2GB (0% used)
    • Hard drive: 450GB unused (out of 500GB drive)
    • AMD Thread Ripper 1950x (16 cores | 32 threads)
    • Problematic tasks: Electrodynamics@home

    Console output:

    This problem looks very much like a DCC server error!

    --

    And on another host, I am getting the following errors:

    Console Output:

    1
    Comment actions Permalink
  • Avatar
    Greg Agnew

    Turns out we are getting hash collisions in ext4 filesystem, and getting ENOSPC.

    As for the other issue, I found where some events where not being properly removed, and so sockets were staying open and you were receiving too many tasks. With the hash-collisions this problem was being compounded.

    We are pushing fixes to these problems. Thank you for reporting them!

    1
    Comment actions Permalink
  • Avatar
    CK-N

    No worries, thanks for the update.

    Are you likely to send out another email when the next update goes live? (as for now I have turned off DCC miner for all hosts).

    Something else I forgot to mention, when the tasks were running (including just a single one), around 30%-50% of a GTX 1080Ti was being used by DCC. As soon as the DCC task(s) finished/reloaded, the GPU usage dropped back to the normal less than 1% (for screen display)?!

    Could you look into this as DCC should not be using/affecting any attached GPUs; normally (when not troubleshooting) they will be running BOINC GPU projects concurrently with DCC miner hence why we need them fully available.

    All hosts run 1-2 (upto 4) GTX1080 or GTX1080Ti dependent on the current configuration.

    1
    Comment actions Permalink
  • Avatar
    dblanch256

    For what it's worth, I'm am not experiencing any major problems running desktop W10 x64 with i7-3770, NVidia 1060.

    But I have only run it using the BRAVE browser.

    0
    Comment actions Permalink

Please sign in to leave a comment.