[Dev] NeoScrypt GPU Miner - Public Beta Test

fragilefungi

I have left the latest version on overnight, I am getting am 41khash/sec on my nvidia with compute 2.0. I think that is pretty good for an older card. I can get another 7khash/sec if the cpu miner is running on 3 threads. I get 12khash/sec with the cpuminer if I run on 4 threads and mine darkcoin with the gpu.

I still am getting higher cpu usage when the gpu miner is running. I think it runs a lot more stable if I leave one cpu thread free. This might be an area for improving stability in the next version. I think that cgminer right makes everything else run slow because it is using cpu and has a higher priority.

Another option for improvement would be to increase how much cpu that cg miner uses, but just add a setting for how many cpu threads to use. It might run better if one cpu thread is dedicated to all other programs, while cgminer is hashing and controlling the gpu with the other cpu threads.

(My start options are: -I 11 -w32 -g 2 )

kris_davison

What NVidia card are you running fragilefungi?

cisahasa

What do you mean? The accepted shares amount? I am getting around 500k a day at 390 khs

370k shares 24hours at 284khs, compares almost equal to your shares

single best share 13.2M, getting like 2-3 +10M shares a day, is it too much luck?

WU value is out of control, its showing what ever it likes

prensel

I’ve pointed some mining power to theblocksfactory on the PXC pool :-)

cisahasa

I’ve pointed some mining power to theblocksfactory on the PXC pool :-)

2.18 MH/s?

prensel

I’ve pointed some mining power to theblocksfactory on the PXC pool :-)

2.18 MH/s?

Yep :-)

But just moved most of it over to p2pool

rynomite

Having the best luck as mentioned earlier by using bin files created with 13.11 and then installing the 14.X drivers. Seems that the R9 290 doesn’t understand the -g 2 option without the newer drivers installed (makes a big difference in hash rate for the R9 290). I’ve got my 7950’s hashing at 85Kh/s and my R9 290 (hynix) at 111Kh/s. using -g 2, -I 13 (7950’s), 14 (r9 290) and -w 32 for both. My 7950’s are OC’d, the 290 is running stock clocks and undervolted. Running 3.7.7b.

prensel

How did you undervolt the 290 ?

Edosterman

Where is the lastest cgminer source available?

thanks,

freeapp

Hi,

did anybody get it run on a iMAC?

I get only about 1-2 KH/s and system is very unusable. My iMAC is late 2011, with AMD HD6770M.

I got “normal” hashrates for scrypt, keccak and so on…

./cgminer --neoscrypt -I 8 -o urltotheblocksfactory -u user -p passwort

build with latest source from https://github.com/vehre/neo-gpuminer

regards,

freeapp

ghostlander

It isn’t a Mac related problem, it’s VLIW5/VLIW4 architecture. If a kernel isn’t vectorised, it performs terrible. That’s what you see. If it is, the performance is excellent. For example, Myriad-Groestl delivers 11.5MH/s for HD5870 (Scrypt 400KH/s), 15MH/s for HD6970 (Scrypt 500KH/s), 17MH/s for R9 280X (Scrypt 700KH/s). I hope the situation will change soon.

rynomite

How did you undervolt the 290 ?

I’m using MSI Afterburner. Most of mine seem to run pretty stable at -62 with stock clocks.

Lukey_p

Hi all, with a GTX780 i can get cgminer to start running 3.7.1 but 3.7.7b i get the following error:

Failed to init GPU thread 0, disabling device 0

Restarting the GPU from the menu will not fix this.

Try restarting cgminer.

i tried replacing the file as mentioned on the 1st page.

Is it an issue with having an NVIDIA GTX780?

Thanks

Wellenreiter

the error is often related to a missing or wrong .cl file.

you need the file neoscrypt140909.cl in the directory you use as working directory, when you start cgminer. after compile the file is in the directory the new made cgminer binary resides in.

I have a NVIDIA GTX 750Ti and 3.7.7b is working fie for me

kris_davison

What hash rate are you getting from your 750ti?

Wellenreiter

it’s ~ 40khash/sec at I= 13 no special tuning

Card takes 70 W of power

Alpha Wolf

Found a little time to play with the newest cgminer, here are my findings, tested with many different settings. -w 16 produced the best khash of all tested. 8 to 512

3.7.7b config 2x R9 270 non X did work up to -I 15 but OS became unresponsive with little to no gain in hash rate, -I 13 best hash and feel for system.

also running minerd 22 CPU cores Solo locked to 23 CPU cores, GPU locked to CPU core 0… 37kh/s per GPU or 75kh/s for the pair.

{
"pools" : [
	{
		"url" : "stratum+tcp://yourp2poolhere.org:10554",
		"user" : "WalletAddress",
		"pass" : "x"
	}
]
,
"intensity" : "13,13",
"vectors" : "1,1",
"worksize" : "16,16",
"gpu-engine" : "1100-1100,1100-1100",
"gpu-fan" : "0-85,0-85",
"gpu-memclock" : "1450,1450",
"gpu-memdiff" : "0,0",
"gpu-powertune" : "0,0",
"gpu-vddc" : "0.000,0.000",
"temp-cutoff" : "90,90",
"temp-overheat" : "85,85",
"temp-target" : "70,70",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "1",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "1",
"log" : "5",
"neoscrypt" : true,
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "1",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"device" : "0-1"
}

mirrax

Found a little time to play with the newest cgminer, here are my findings, tested with many different settings. -w 16 produced the best khash of all tested. 8 to 512

3.7.7b config 2x R9 270 non X did work up to -I 15 but OS became unresponsive with little to no gain in hash rate, -I 13 best hash and feel for system.

also running minerd 22 CPU cores Solo locked to 23 CPU cores, GPU locked to CPU core 0… 37kh/s per GPU or 75kh/s for the pair.
{
"pools" : [
	{
		"url" : "stratum+tcp://yourp2poolhere.org:10554",
		"user" : "WalletAddress",
		"pass" : "x"
	}
]
,
"intensity" : "13,13",
"vectors" : "1,1",
"worksize" : "16,16",
"gpu-engine" : "1100-1100,1100-1100",
"gpu-fan" : "0-85,0-85",
"gpu-memclock" : "1450,1450",
"gpu-memdiff" : "0,0",
"gpu-powertune" : "0,0",
"gpu-vddc" : "0.000,0.000",
"temp-cutoff" : "90,90",
"temp-overheat" : "85,85",
"temp-target" : "70,70",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "1",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "1",
"log" : "5",
"neoscrypt" : true,
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "1",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"device" : "0-1"
}

Thanks, I also have R9 270.

Will start with your settings ;)

Alpha Wolf

Seems I’m getting a bit more rejects with 3.7.7b than I was with 3.7.5, still within tolerance I believe, was a max of 22kh/s per card with 3.7.5, so I like the gain in k.

mirrax

Howto

Getting started with gpuminer

Linux: Get the program

download latest version from github here.

extract the zip file into an empty directory.

Linux: Compile the program (Detailed build FAQ coming soon)

change into that directory anr run ‘autogen.sh’

correct any errors that may be show. Typically some build tools may be missing.

run ‘make’ and optional ‘make install’ as root.

Run cgminer

run “cgminer --neoscrypt -o http://: -O :” *without the “quotes”

Is this part of guide still actuall?

I mean when I download this and version from 0.8.7.0 announce thread I get something totaly different.