CCminer(SP-MOD) Modded GPU kernels.

[HoY]

Yes, +180 +180 with factory overclocked MSI cards. the hashrate is usually slightly higher on 2 of those cards but when I'm connected on teamviewer to that rig they both slow down 100-200kh/s each. been pretty consistent and I haven't found a simple solution to that

[chrysophylax]

Yes, +180 +180 with factory overclocked MSI cards. the hashrate is usually slightly higher on 2 of those cards but when I'm connected on teamviewer to that rig they both slow down 100-200kh/s each. been pretty consistent and I haven't found a simple solution to that

nice ... so the assumption is that its a windows system then ...

if so - try the rdp connection thats built in to windows instead of teamviewer ... im a teamviewer advocate also - but in this instance - i would find a way to keep track with as little overhead as possible ...

or switch to linux ...

the only thing im missing knowledge ( and not many can answer this without actually modding the card itself ) is the method of overclocking within linux itself ...

sgminer is quite granular and can change settings via commandline ... ccminer has no such thing that i know of - apart from the intensity setting ... and that doesnt seem to be doing much at all at the moment ...

still - nice hashrates ...

#crysx

[HoY]

I chose and stuck with teamviewer for its cross platform simplicity. That, and not having to manage all the port forwarding across the 10 rigs i have in my little farm. Teamviewer lets me connect easily from my iphone, from which I do most of my work while I am away from home. I have been considering switching to linux, however my farm is 4500km away on the other side of the country, and I already burden my brother with enough hardware troubleshooting as it is!

[chrysophylax]

I chose and stuck with teamviewer for its cross platform simplicity. That, and not having to manage all the port forwarding across the 10 rigs i have in my little farm. Teamviewer lets me connect easily from my iphone, from which I do most of my work while I am away from home. I have been considering switching to linux, however my farm is 4500km away on the other side of the country, and I already burden my brother with enough hardware troubleshooting as it is!

hence the reason to go with linux ...

the control over the system via console is unparalleled ... and im in a similar situation as you are with the systems when im not here in the office ...

a simple boot and ssh daemon activation on the main system ( or pxe boot with scripts to auto install with your settings ) or even a prebuilt mining package ( which i dont use as i want my own setup - hence why i use fedora on the miners ) and viola - done in a matter of a few minutes ... o - and its free ...

anyway - teamviewer is a great little package and if it serves you well - then all good i say ...

need to run some errands - then will be back to build another system with nvidia cards ... testing with one first though - and the latest compile of ccminer ... so see you in about two hours ...

#crysx

[restless]

Is this build supporting cryptonight?!

[Handofmidas]

Good job as always SP! Lyra2 hash is a bit better.

However, same issue as with x11: Pool does not report the full hashrate. I think this is a ccminer 1.5.x related problem. For the original ccminer-Lyra2RE, pools show the correct hashrate as it is displayed in the miner. Would you mind to include the Lyra2 improvements into djm34's ccminer-Lyra2RE release?

I have done some fixes in x11 , is it still underrepporting in release 21?

Lyra is currently only finding one solution and the throughput is big. I will add 2 solutions soon.

I am considering to change the fork to the DJM34 fork. Clean it and replace all the kernals.

1. Less crashes.
2. Fix the problem on some pools.

But will lack some features like the API etc..

Hi, hope you guys had a good Christmas! As promised earlier, I have tested X11 with release21, and the hashrate is still not fully recognized by (some?) pools. Here's the graph for 16h of mining.

[chrysophylax]

Good job as always SP! Lyra2 hash is a bit better.

However, same issue as with x11: Pool does not report the full hashrate. I think this is a ccminer 1.5.x related problem. For the original ccminer-Lyra2RE, pools show the correct hashrate as it is displayed in the miner. Would you mind to include the Lyra2 improvements into djm34's ccminer-Lyra2RE release?

I have done some fixes in x11 , is it still underrepporting in release 21?

Lyra is currently only finding one solution and the throughput is big. I will add 2 solutions soon.

I am considering to change the fork to the DJM34 fork. Clean it and replace all the kernals.

1. Less crashes.
2. Fix the problem on some pools.

But will lack some features like the API etc..

Hi, hope you guys had a good Christmas! As promised earlier, I have tested X11 with release21, and the hashrate is still not fully recognized by (some?) pools. Here's the graph for 16h of mining.

from what i can gather with all the mining thats been done - there is NO pool that will give a totally accurate hashrate ...

this is due to the collation of the previous accepted shares and the hashrate is calculated on THOSE accepted shares only for the period of time that the pool takes the sample shares ... most pools take this period of time to be 10 minutes - but some longer ...

this means that no matter what the miner itself says its doing - the pool will not show the same ...

this is why we can only get an _estimate_ of what the hashrate may be from the pools - and a more _accurate estimate_ from the miner itself ...

the hashrates from the miner are usually around the same figure - with a small splay percentage ...

the hashrates from the pools are usually much more splayed and have a higher degree of variance ...

result? ... the most accurate representation of hashrate is from the miner itself ...

thats my take on it anyway ... can anyone shed more light on this situation? ...

#crysx

[sp_]

The problem is that when after I merged my kernals into 1.5.0 and above, the rate has gone down on some pools. Release 8 or 9 is displaying the full hash(1.4.9-mod). The only way to test for sure is to merge kernals down to the
djm34 release. This is some hours work. I will merge the kernals and then release a test build. I plan to fix the bug in the latest version, but the merging is needed to find the bug.

10 accepted in 1 minute is a bit high. You should increase the difficulty or use vardiff.

[tbearhere]

Nice graph The new version seems to have more stable hashrate. I am working to remove some cpu load for the next build

With 22 I got improvement some but a lot more power usage. My team-viewer crashes sometimes with 22. I'm back to 21 release, waiting for 23.
Yes, less cpu usage would be great. 

[scryptr]

Version 22 unstable? --

I also dropped v22, and returned to tpruvot's 1.5.2-git work.  I hope that your improved hashing routines make it into his version soon; there was a real increase in performance.  I'll probably try v23 as soon as it is up.

My slower rig has a Sempron 145, 8 gigs ram.  It would work well for 12 hours or so, then the hash rate would drop to a crawl and the rig would crash.  The faster rig is holding its own and I will let it be with v22.  It has a faster AMD FX CPU.  Maybe a memory leak?       --scryptr

[sp_]

I have checked in a fix now on gihub. The cpu usage is reduced to 1/3 in x11. Hashrate is the same as in 22.

building 23 now.

[sp_]

Fixed slow cpu. X11,x13,x14,x15,x17, nist, quark. Lyra is still a bit slow but faster than build 22


The 23nd public beta(windows executable) is available here: (29-12-2014)

http://www.filedropper.com/ccminer23

The sourcecode is available here:

https://github.com/sp-hash/ccminer

Post your stats here. Card name/gpu clock/memclock

[Bombadil]

Fixed slow cpu. X11,x13,x14,x15,x17, nist, quark. Lyra is still a bit slow but faster than build 22


The 23nd public beta(windows executable) is available here: (29-12-2014)

http://www.filedropper.com/ccminer23

The sourcecode is available here:

https://github.com/sp-hash/ccminer

Post your stats here. Card name/gpu clock/memclock

Same hashrate on X11 but only 12% cpu usage now ^^ It was 8% before build22 for 2x 750TIs. Thx.


(Started build23 after the last red area/line, ignore the others )

Now let's hope you'll keep the API so I can keep on monitoring.
I'm nearing the first release of it, and it would be a real shame if all was for nothing.
Source of almost-100%-working ccmonitor is already out there: https://github.com/KBomba/ccmonitor

[K1773R]

Fixed slow cpu. X11,x13,x14,x15,x17, nist, quark. Lyra is still a bit slow but faster than build 22


The 23nd public beta(windows executable) is available here: (29-12-2014)

http://www.filedropper.com/ccminer23

The sourcecode is available here:

https://github.com/sp-hash/ccminer

Post your stats here. Card name/gpu clock/memclock

Same hashrate on X11 but only 12% cpu usage now ^^ It was 8% before build22 for 2x 750TIs. Thx.


(Started build23 after the last red area/line, ignore the others )

Now let's hope you'll keep the API so I can keep on monitoring.
I'm nearing the first release of it, and it would be a real shame if all was for nothing.
Source of almost-100%-working ccmonitor is already out there: https://github.com/KBomba/ccmonitor

does it work with mono?

[tbearhere]

About 50kh  more on quark with no intensity settings. With #23 750ti.

[Bombadil]

does it work with mono?

No idea, and I won't get my hopes up for it ^^" But it works over the network, so another windoze pc or virtualbox with its own network connection should work.

[jpouza]

Just rolled back to release 21, 6% CPU usage against 44% of release 22.

[K1773R]

does it work with mono?

No idea, and I won't get my hopes up for it ^^" But it works over the network, so another windoze pc or virtualbox with windoze should work.

winblows is no option

[Bombadil]

Just rolled back to release 21, 6% CPU usage against 44% of release 22.

There's release 23 already: https://bitcointalk.org/index.php?topic=826901.msg9976879#msg9976879

does it work with mono?

No idea, and I won't get my hopes up for it ^^" But it works over the network, so another windoze pc or virtualbox with windoze should work.

winblows is no option

Aahw. Well seeing you're a Legendary and you've managed to stick with the game for so long, you'll probably have deeprooted ideals in which Windoze doesn't fit ^^"
Well, I'm sorry to say, but I'm just an autodidact when it comes to programming, IRL I'm an ISP technician, so don't expect that much from me
(/me should've just sticked with java, but no, C# just had to be more powerful )

[jpouza]

Just rolled back to release 21, 6% CPU usage against 44% of release 22.

There's release 23 already: https://bitcointalk.org/index.php?topic=826901.msg9976879#msg9976879

Tks!