burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms)



  • @gpedro the IP one didnt work for me at all so no wonder there. Not sure why others doesnt work tho (thus recommendation to try local and see what happens :D )



  • I'm running a AMD r9 280x with 16.11.5 and AMD SDK 3.0

    I tried 0.4.9 and 0.4.10 - without any luck - my Card never gets detected at the first plattform overwiew. What is wrong here? Any suggestions?

    Windows 10 x64
    i7 4770
    r9 280x


  • admin

    @gpedro you can leave 'walletServer=' empty (disable infos) or try 'walletServer=http://burstcoin.cc:8889'
    not sure, but https may be a issue choose wallet without if thats the case ... at burstcoin.cc you will find some.


  • admin

    @Zaziki If you know platform and device just specify it manualy ...
    e.g.

    platformId=2
    deviceId=1
    

    The platform overview is just a info and maybe not detects exotic setups?! not sure ...
    May also be a driver issue. Have you checked opencl-z if it shows up there?



  • @luxe that worked hehehe
    thanks bro!


  • admin

    @gpedro Well guess i have to check why https does not work ... i expected miners to use localhost :-) Never tested something else ...



  • @luxe yeah I thought so but I still didn't got the local wallet running on this PC hehe



  • got it Running, but for now pretty slow.
    I have about 92TB, Read times ~2min 34s
    With Blago i need about 52s in i7 4770.

    there must be sth wrong.

    All my plots are optimized and One File per Drive.

    I Read that r9 280x only Support opencl 1.2, is there maybe the Problem?



  • i tried to solo mine but even though its set up properly, local wallet up to date, I see blocks won by others but my disks aren't being read so its not mining. In actual fact, the disks have gone to sleep lol. Any suggestions? is there some sort of limitation such as passphrase length?


  • admin

    @Zaziki 280x is fine ... are you sure you use it? Please provide more details like screen of miner and/or your config.

    @ZapbuzZ The miner will start mining as soon the connected wallet receives a new block ... if you provide your config i can take a look on it (without passphrase ... that is not limited as far as i know).



  • ok ty @luxe thanks for information. i decided to go to a pool for now. If I decide to mine solo mode again i will post the config.



  • @Luxe, note that in the config file the target deadline is listed in the solo section of the code, as if it's not applicable to pool mining. There are some pools, specifically the Lex code that does not override this value so it will apply when pool mining on Lex code pools. If someone sets up a short Target DL like 14400 for solo mining and forgets about it and swaps over to a lex code pool they will loose many DL submissions as skipped.

    On your next revision, you may want to consider moving it into a more general section of the file. Just a thought.



  • @luxe Sorry for my late answer.

    After finishing plotting, times got better - but still i think that 1400MB/s are not that fast. I read that u do 3500 with the same GPU.

    Here Some Screens (startupInfo, plotted Files, oneBlock)

    alt text alt text alt text

    Some Info:
    I have 6 Drives at the Mainboard internal SATA Controller (SATA6G).
    Another 3 Drives are at a Adaptec 6805E Controller
    all other Drives are connected via USB 3.0


  • admin

    @Zaziki i have more drives/controllers than you, due to parallel reading i reach higher MB/s (~30 sec round time is fine) ... your setup so far looks very good. Btw. you can mount drives to directories, you do not need to assign a-z drive letters ... https://technet.microsoft.com/en-us/library/cc753321(v=ws.11).aspx#BKMK_WINUI



  • @luxe thanks mate



  • My setup:

    • 19x 8 TB disks: 8x SATA mainboard, 3x SATA PCIe Controller, 8x USB 3.0 (PCIe controller with 4 USB 3.0 controller chips, 2 disks each port/controller)
    • AMD A8-7670K APU with R7 cores used for jminer
    • burstcoin-jminer v0.4.10 with Win10 x64

    What's going wrong / questions:

    1. All 11 internal SATA disks are read out first and when they finished their work, all USB 3.0 are read out. Is this kind of prioritization a bug or a feature? I believe I loose a lot of time because of that.
    2. What does the "GB" number mean. All internal SATA disks show "0GB" and all USB 3.0 disks "1GB".
    3. Is it somehow possible to show the "100% done...". message only? Just a cosmetic issue. :-)
    4. What does the "avg." and "eff." value mean exactly? First one is "average" but what's the second one?

    alt text

    Thanks!



  • @eneloop 1. I would guess that the R7 does not have enough threads to spawn one for each of your drives, so it has to recycle the threads after they're done reading the first dozen or so drives. You'll probably need a discreet GPU to turn those 70 second read times into 35 second ones.

    1. The GB number is just size. Some of your 8TB drives seem to be a bit larger than 8TB. Lucky you.
    2. Modify the source code and recompile and you can make it say whatever you like. :)
    3. Dunno this one.


  • @sevencardz said in burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms):

    @eneloop 1. I would guess that the R7 does not have enough threads to spawn one for each of your drives, so it has to recycle the threads after they're done reading the first dozen or so drives. You'll probably need a discreet GPU to turn those 70 second read times into 35 second ones.

    1. The GB number is just size. Some of your 8TB drives seem to be a bit larger than 8TB. Lucky you.
    2. Modify the source code and recompile and you can make it say whatever you like. :)
    3. Dunno this one.
    1. you don't have to modify the source code. There is a switch, "readProgressPerRound", in the config file. If you set it for 10 it will read out in 10% increments. If you set it for 2 it will readout 51 and 100. Set it for 1 and it should give you 1% and 100%.

    2. Pretty sure average is for that readout segment, effective over the entire round.



  • @sevencardz said in burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms):

    @eneloop 1. I would guess that the R7 does not have enough threads to spawn one for each of your drives, so it has to recycle the threads after they're done reading the first dozen or so drives. You'll probably need a discreet GPU to turn those 70 second read times into 35 second ones.

    1. The GB number is just size. Some of your 8TB drives seem to be a bit larger than 8TB. Lucky you.
    1. I don't think this issue is related to the number of threads because I tried the same with only 5 internal disks. With 5 disks the times are better (because of less disks) but the USB disks are still idleing while the internal ones are read out. With 5 internal disks, additional 6 USB disks have to be read out at the same time if the limit is 11.

    1. The size of what is read from each disk? If yes, then jminer is not rounding. It shows 1GB only when it's at least 1GB. Wright?
      Yes, they are from different manufacturers.

    @rds said in burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms):

    @sevencardz said in burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms):

    @eneloop 1. I would guess that the R7 does not have enough threads to spawn one for each of your drives, so it has to recycle the threads after they're done reading the first dozen or so drives. You'll probably need a discreet GPU to turn those 70 second read times into 35 second ones.

    1. The GB number is just size. Some of your 8TB drives seem to be a bit larger than 8TB. Lucky you.
    2. Modify the source code and recompile and you can make it say whatever you like. :)
    3. Dunno this one.
    1. you don't have to modify the source code. There is a switch, "readProgressPerRound", in the config file. If you set it for 10 it will read out in 10% increments. If you set it for 2 it will readout 51 and 100. Set it for 1 and it should give you 1% and 100%.

    2. Pretty sure average is for that readout segment, effective over the entire round.

    1. I have that switch already enabled set to 1. As you say this gives me 1 and 100...only 100% would be fine. :-)
    2. Ok, thank you!

  • admin

    @eneloop said in burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms):

    My setup:

    • 19x 8 TB disks: 8x SATA mainboard, 3x SATA PCIe Controller, 8x USB 3.0 (PCIe controller with 4 USB 3.0 controller chips, 2 disks each port/controller)
    • AMD A8-7670K APU with R7 cores used for jminer
    • burstcoin-jminer v0.4.10 with Win10 x64

    What's going wrong / questions:

    1. All 11 internal SATA disks are read out first and when they finished their work, all USB 3.0 are read out. Is this kind of prioritization a bug or a feature? I believe I loose a lot of time because of that.
    2. What does the "GB" number mean. All internal SATA disks show "0GB" and all USB 3.0 disks "1GB".
    3. Is it somehow possible to show the "100% done...". message only? Just a cosmetic issue. :-)
    4. What does the "avg." and "eff." value mean exactly? First one is "average" but what's the second one?

    alt text

    Thanks!

    1. No, they may finish after the internal ones, but they should all read parallel, as long every plotPath points to one physical drive ... jminer uses one thread for every plotPath.
      Ensure you have 'readerThreads=0' having this setting changed could lead to your problems.
      As it would limit the threads in reader thread pool.
    2. the size is calculated by the plotfile names
      Linke @rds said:
    3. 'readProgressPerRound=0' and 'showDriveInfo=false' and 'showSkippedDeadlines=false'
    4. avg = over the whole round, eff. = since last log ... e.g. perfect configured setup would not get slower/lower eff. in the end.

Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.