CryptoDredge 0.27.0 — CUDA Miner - page 44.

cryptodredge

member

Activity: 157

Merit: 19

Quote from: jyakulis on August 05, 2018, 09:27:54 PM

0.8 to 0.8.2 was a big boost on lyra2z for the gtx1070 (2500 kh/s to 3200 kh/s)

However, 0.8 to 0.8.2 the hashrate regressed on lyra2z for the gtx1070ti (3300 kh/s to 2700 kh/s)

Quote from: bruutje on August 06, 2018, 08:41:57 AM

love the improvements.
However since 0.8.2 my 1070 greatly outperforms my 1070ti's on Lyra2z.

1070 avg hash 3954 KH/s
1070ti avg hash 3220 KH/s

any ideas how? I've got 4 different 1070ti's and none come close to my normal 1070.... Sad

Could you check v0.8.3?

cryptodredge

member

Activity: 157

Merit: 19

Quote from: cryptoteh on August 06, 2018, 12:22:58 AM

Quote from: cryptodredge on August 04, 2018, 05:21:35 AM

Quote from: cryptoteh on August 04, 2018, 03:53:30 AM

How to set the intensity of the first graphics card 3 and the second 6?

No way. As a workaround for this issue, you might use a few CryptoDredge instances with -d option.
e.g.:

Code: (first.bat)

CryptoDredge -a -o stratum+tcp:// -u -p -d 0 -i 3

Code: (second.bat)

CryptoDredge -a -o stratum+tcp:// -u -p -d 1

Can we expect this option? this is very important

The task was created for this feature. Stay tuned.

cryptodredge

member

Activity: 157

Merit: 19

Quote from: sumit.mathur101 on August 06, 2018, 04:21:50 PM

Hello, is there any diff between cuda 9.1 and cuda 9.2?

The difference is not significant. The cu9.2 version faster cu9.1 by about 0.7% (depend on GPU and algorithm)
Tested on 1060 and Phi2

sumit.mathur101

newbie

Activity: 101

Merit: 0

Hello, is there any diff between cuda 9.1 and cuda 9.2?

cryptodredge

member

Activity: 157

Merit: 19

Downloads
Windows Download (CUDA 9.2 version)
Linux Download (CUDA 9.2 version)
Mirror on GitHub (CUDA 9.1/9.2 version)

Release 0.8.3 - (August 7, 2018)

Fix TCP and WebSocket connections used for API
Fix Lyra2z performance on 1070 Ti and P104-100 graphics cards

Happy mining!
The CryptoDredge Team.

Vispilio

legendary

Activity: 2072

Merit: 1618

Quote from: Zorg33 on August 06, 2018, 03:50:04 PM

You simply cannot compare PL % settings of different cards.
Percentages don't tell shit, because it is relative to the TDP set in the BIOS of the particular card.

Card A has TDP 250W (average 1080Ti with AC) and card B has TDP of 280W (1080Ti with LC).
70% means 175W for card A and 196W for card B.
It's obvious that card B will perform faster (if the clock/voltage curve is similar, but that also differs adding more complexity to the problem)

The same logic also applies for Core and Mem clock offsets. +100 means nothing, because 0% GPU clock can be anywhere between 1500 and 2000MHz.
So please stop comparing them among different cards, makes no sense.
You have to compare the exact clocks.

I agree, and that's a good point, but for whatever reasons, both on windows and linux programs like SMOS, a rig runs more stably when you apply a singular OC setting across

the board for all cards attached to that rig. That's why I prefer to initially shoot for general and modest OC settings that would yield efficient results across a wide variety of

card parameters; on top of that, if you really want to tinker with a particular GPU, you can always finetune it further...

Zorg33

jr. member

Activity: 144

Merit: 2

Quote from: Vispilio on August 06, 2018, 03:42:32 PM

How much do you ideally undervolt with CryptoDredge when mining Lyra2Rev2 ?.. Some people go as low as 65 % - 70 %, claiming it's the most efficient, while the

majority prefers 75% - 80%. Of course the lower you go on voltage, you can squeeze more Core overclocking from your cards, but with the proviso that

too much OC causes lots of bad shares, so I would be very interested if anyone found an optimal MSI configuration for this particular miner

You simply cannot compare PL % settings of different cards.
Percentages don't tell shit, because it is relative to the TDP set in the BIOS of the particular card.

Card A has TDP 250W (average 1080Ti with AC) and card B has TDP of 280W (1080Ti with LC).
70% means 175W for card A and 196W for card B.
It's obvious that card B will perform faster (if the clock/voltage curve is similar, but that also differs adding more complexity to the problem)

The same logic also applies for Core and Mem clock offsets. +100 means nothing, because 0% GPU clock can be anywhere between 1500 and 2000MHz.
So please stop comparing them among different cards, makes no sense.
You have to compare the exact clocks.

Vispilio

legendary

Activity: 2072

Merit: 1618

How much do you ideally undervolt with CryptoDredge when mining Lyra2Rev2 ?.. Some people go as low as 65 % - 70 %, claiming it's the most efficient, while the

majority prefers 75% - 80%. Of course the lower you go on voltage, you can squeeze more Core overclocking from your cards, but with the proviso that

too much OC causes lots of bad shares, so I would be very interested if anyone found an optimal MSI configuration for this particular miner

nitrobg

member

Activity: 413

Merit: 17

Quote from: dragonmike on August 06, 2018, 10:05:44 AM

Quote from: dragonmike on August 05, 2018, 02:17:53 PM

Your performance figures on Neoscrypt are a little optimistic...

Using latest nVidia drivers, I get 1230 Mh/s on my 1080's at +110/+500 (vs 1330-1390 advertised above). Intensity at default (6).

...is anyone able to tell me what I'm doing wrong here or is the advertised speed really bogus? Or at 130% pl with 200+ overclocks?... Huh

Increase the intensity. Excavator 1.4.4a is still the best miner for neoscrypt.

flameelement

newbie

Activity: 4

Merit: 0

Hi,
How to run power consumption?
Regards.

webgkv

newbie

Activity: 57

Merit: 0

It's works in different way with different algo, same like this:

{"Allium": "-a allium -b 127.0.0.1:4068"},
{"blake2s":"-a blake2s"},
{"lyra2v2" : "-a lyra2v2 --api-type ccminer-tcp -b 127.0.0.1:4068 "},
{"lyra2z" : "-a lyra2z -b 127.0.0.1:4068" },
{"Neoscrypt":"-a neoscrypt --api-type ccminer-tcp -b 127.0.0.1:4068 " },
{"phi":"-a phi -b 127.0.0.1:4068"},
{"skein" : "-a skein -b 127.0.0.1:4068"},
{"skunk":"-a skunk -b 127.0.0.1:4068"},
{"Tribus":"-a tribus --api-type ccminer-tcp -b 127.0.0.1:4068"}

After restart it's can needs to change for only "-b 127.0.0.1:4068" or also also

0.8 work in API mode by default on all algo grate, Please! back it!

superlative1974

newbie

Activity: 45

Merit: 0

Quote from: cryptodredge on August 06, 2018, 08:44:54 AM

Quote from: superlative1974 on August 06, 2018, 08:35:56 AM

Quote from: cryptodredge on August 05, 2018, 02:43:49 PM

Quote from: jebidia on August 05, 2018, 02:38:54 PM

CD .6 and up are no longer working on PHI2 after fork...please advise

Cryptodredge has problems with Lux's smart contracts.

We'll try to fix it as soon as possible. Sorry for the inconvenience!

Hello, PHI2 works great.
question. you can make under the algoritm HEX, it's possible, you would be the first))))

Thanks for your suggestion. Could you provide the specification of the HEX algo?

coin xDNA "Hex" -Algo
the algorithm is new, only this coin has this algo, you would become a leader, the xDNA community is very large, the algorithm "Hex" only for video cards
https://github.com/XDNA-Core/ccminer-hex

dragonmike

hero member

Activity: 1274

Merit: 556

Quote from: dragonmike on August 05, 2018, 02:17:53 PM

Your performance figures on Neoscrypt are a little optimistic...

Using latest nVidia drivers, I get 1230 Mh/s on my 1080's at +110/+500 (vs 1330-1390 advertised above). Intensity at default (6).

...is anyone able to tell me what I'm doing wrong here or is the advertised speed really bogus? Or at 130% pl with 200+ overclocks?... Huh

terryborg

newbie

Activity: 18

Merit: 0

Quote from: cryptodredge on August 06, 2018, 07:25:18 AM

Quote from: sidog on August 05, 2018, 09:06:31 PM

the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?

Quote from: Burnie on August 05, 2018, 10:53:14 PM

Does CryptoDredge close the sockets properly before exiting?
I see a lot of TIME_WAITs when CryptoDredge is running, and they slowly disappear when CryptoDredge is stopped.
If CryptoDredge is started after 3-4 minutes, the api seems to start ok.

Quote from: darkneorus on August 05, 2018, 11:06:51 PM

yup, often the miner tries to use the default API bind address and port (127.0.0.1:4068) instead of using the address from its command line arguments.

Quote from: pgj69 on August 06, 2018, 01:20:09 AM

With 0.8.2 the API server is not always started as set by the command line.

Quote from: terryborg on August 06, 2018, 03:13:34 AM

Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.
thanks

Quote from: elkiki1 on August 06, 2018, 06:25:05 AM

+1 on API fix, good miner but unusable by most of us in actual state!

Quote from: BartVanseer on August 06, 2018, 05:48:58 AM

It still mines correctly but you cannot see what you are making and awesome miner will restart the miner because the accepted share does not increase.. need a fix quickly

This bug has already been fixed, update will be delivered soon. What OS do you use?

Win7 X64 ,
thanks

darkneorus

jr. member

Activity: 238

Merit: 3

Quote from: elkiki1 on August 06, 2018, 08:48:54 AM

Win 8.1 x64 here and latest nvidia drivers 398+

difference i notice at start with earlier version is it just seem to ignore the -b option , we no more see the api init message

^^ this. or the miner shows 127.0.0.1:4068 as an API bind address. then after restarting it several times the problem goes away and API works OK again. Roll Eyes

AcharyaOne

newbie

Activity: 36

Merit: 0

windows 10 x64, same issue

cryptodredge

member

Activity: 157

Merit: 19

Quote from: bruutje on August 06, 2018, 08:41:57 AM

love the improvements.
However since 0.8.2 my 1070 greatly outperforms my 1070ti's on Lyra2z.

1070 avg hash 3954 KH/s
1070ti avg hash 3220 KH/s

any ideas how? I've got 4 different 1070ti's and none come close to my normal 1070.... Sad

We'll try to fix it today. Stay tuned!

elkiki1

newbie

Activity: 11

Merit: 0

Win 8.1 x64 here and latest nvidia drivers 398+

difference i notice at start with earlier version is it just seem to ignore the -b option , we no more see the api init message

UselessGuru

jr. member

Activity: 200

Merit: 3