Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come

[blaaaaacksuit]

I might be interested in buying a few of these.  How much are they being traded for amongst you all?  PM me if you want to make an offer.

[1713257864]

1713257864

[1713257864]

1713257864

[1713257864]

1713257864

[paulthetafy]

I might be interested in buying a few of these.  How much are they being traded for amongst you all?  PM me if you want to make an offer.

PM sent

[paulthetafy]

I've mined a good few blocks today and am willing to sell some of it, as I know it has been hard to solo mine.  I don't want to take the piss with prices or start a price war, so please PM me if you want to by some and make me an offer.  I'm happy to donate some to a faucet too if anyone get's one up and running.

This offer is still open.  My intention here is help distribute some coins to those who have solo mined so far without success, so I am open to sensible offers.   Please PM me

Curious how many blocks you found today, I did well about 12hours ago but no blocks for 8hours or so now.

It's certainly got a lot harder as a lot more miners have joined now I think.  Pools will be needed fairly soon.  It took me a little while to get my miners running (damn linux) so I missed the first few hours but got some blocks after that.  It's slowed down a lot now though but I have had blocks today. 


On a different note, I tried fixing the segmentation fault last night by introducing a mutex when retrieving new blocks.  But I then found I was getting the occasional deadlock so I've done something wrong somewhere   I'll take another look tonight.

[fandesase]

No law will automatically stop mining! !

[Videlicet]

Added Mutex Locks to Primeminer, new source on my Github. Still encountered Segmentation Fault though 
Let me know your results as a degree of improvement.

Thank You,
Viz.

[merc84]

Bit rusty on linux still; did "git pull" to update but ubuntu@ubuntu:~/primeminer$ make clean
make: *** No rule to make target `clean'.  Stop.
how to clean build?

Edit: Might be worth mentioning only getting segfault from previous build on i7 4770k, i5 3570k has run since launch without segfault.

[paulthetafy]

Bit rusty on linux still; did "git pull" to update but ubuntu@ubuntu:~/primeminer$ make clean
make: *** No rule to make target `clean'.  Stop.
how to clean build?

Edit: Might be worth mentioning only getting segfault from previous build on i7 4770k, i5 3570k has run since launch without segfault.

make -f makefile.unix

or make -j8 -f makefile.unix (the 8 being number of threads to build with)

[merc84]

Bit rusty on linux still; did "git pull" to update but ubuntu@ubuntu:~/primeminer$ make clean
make: *** No rule to make target `clean'.  Stop.
how to clean build?

Edit: Might be worth mentioning only getting segfault from previous build on i7 4770k, i5 3570k has run since launch without segfault.

make -f makefile.unix

or make -j8 -f makefile.unix (the 8 being number of threads to build with)

I know the cmd to compile    I was wondering how to remove the already built files, from memory with other miners i've run "make clean"

Edit: Also the output of the new build seems "strange" the Meters output seems much much slower than previous build.

[METERS] 22679.023529 SPS | 31.741176 PPS | Height = 1592
[METERS] 25558.700000 SPS | 46.600000 PPS | Height = 1592
[METERS] 70294.142857 SPS | 110.142857 PPS | Height = 1592
[METERS] 51540.625000 SPS | 59.750000 PPS | Height = 1592
[METERS] 38107.833333 SPS | 50.500000 PPS | Height = 1592
[METERS] 44799.000000 SPS | 84.500000 PPS | Height = 1592
[METERS] 58842.166667 SPS | 75.666667 PPS | Height = 1592
[METERS] 64534.800000 SPS | 123.900000 PPS | Height = 1592
[MASTER] Coinshield Network: New Block 1593
[METERS] 42817.125000 SPS | 32.562500 PPS | Height = 1593
[METERS] 27897.500000 SPS | 51.125000 PPS | Height = 1593
[METERS] 39008.250000 SPS | 65.625000 PPS | Height = 1593
[MASTER] Coinshield Network: New Block 1594
[METERS] 29257.444444 SPS | 35.444444 PPS | Height = 1594
[METERS] 54324.333333 SPS | 120.000000 PPS | Height = 1594

Edit2: Then some connection issue to the wallet, previous build is chugging away fine on another machine.
[MASTER] Coinshield Network: New Block 1595
[METERS] 32235.000000 SPS | 39.800000 PPS | Height = 1595
[METERS] 89994.000000 SPS | 203.000000 PPS | Height = 1595
Failed to Update Height...

[Hix]

What your previous build METERS result?

[merc84]

previous build was ~ 33PPS

[paulthetafy]

Bit rusty on linux still; did "git pull" to update but ubuntu@ubuntu:~/primeminer$ make clean
make: *** No rule to make target `clean'.  Stop.
how to clean build?

Edit: Might be worth mentioning only getting segfault from previous build on i7 4770k, i5 3570k has run since launch without segfault.

make -f makefile.unix

or make -j8 -f makefile.unix (the 8 being number of threads to build with)

I know the cmd to compile    I was wondering how to remove the already built files, from memory with other miners i've run "make clean"

Edit: Also the output of the new build seems "strange" the Meters output seems much much slower than previous build.

[METERS] 22679.023529 SPS | 31.741176 PPS | Height = 1592
[METERS] 25558.700000 SPS | 46.600000 PPS | Height = 1592
[METERS] 70294.142857 SPS | 110.142857 PPS | Height = 1592
[METERS] 51540.625000 SPS | 59.750000 PPS | Height = 1592
[METERS] 38107.833333 SPS | 50.500000 PPS | Height = 1592
[METERS] 44799.000000 SPS | 84.500000 PPS | Height = 1592
[METERS] 58842.166667 SPS | 75.666667 PPS | Height = 1592
[METERS] 64534.800000 SPS | 123.900000 PPS | Height = 1592
[MASTER] Coinshield Network: New Block 1593
[METERS] 42817.125000 SPS | 32.562500 PPS | Height = 1593
[METERS] 27897.500000 SPS | 51.125000 PPS | Height = 1593
[METERS] 39008.250000 SPS | 65.625000 PPS | Height = 1593
[MASTER] Coinshield Network: New Block 1594
[METERS] 29257.444444 SPS | 35.444444 PPS | Height = 1594
[METERS] 54324.333333 SPS | 120.000000 PPS | Height = 1594

Edit2: Then some connection issue to the wallet, previous build is chugging away fine on another machine.
[MASTER] Coinshield Network: New Block 1595
[METERS] 32235.000000 SPS | 39.800000 PPS | Height = 1595
[METERS] 89994.000000 SPS | 203.000000 PPS | Height = 1595
Failed to Update Height...

You still have to provide the make file was my point.
So make clean -f makefile.unix

[yampi]

I compiled miner with cygwin and the PPS rate went up greatly.

[merc84]

thanks Paul 

[Hix]

previous build was ~ 33PPS

Why say "much much slower" if you have same results?)

[METERS] 22679.023529 SPS | 31.741176 PPS | Height = 1592

[merc84]

previous build was ~ 33PPS

Why say "much much slower" if you have same results?)

[METERS] 22679.023529 SPS | 31.741176 PPS | Height = 1592

Sorry for the confusion but the actual display of the output happens less often. I hope that makes sense.

[paulthetafy]

previous build was ~ 33PPS

Why say "much much slower" if you have same results?)

[METERS] 22679.023529 SPS | 31.741176 PPS | Height = 1592

Sorry for the confusion but the actual display of the output happens less often. I hope that makes sense.

Yeah that makes sense and I'm seeing the same result.  I'm also seeing very frequent segmentation faults still which is not good.  Maybe hold off on this miner until it is resolved.

[paulthetafy]

Added Mutex Locks to Primeminer, new source on my Github. Still encountered Segmentation Fault though 
Let me know your results as a degree of improvement.

Thank You,
Viz.

Viz, I think you can simplify your solution by moving the mutex lock in the ServerThread loop INSIDE the if(BLOCK) statement around line 313 of miner.cpp. 

Code:

if(BLOCK)
{
LOCK(THREADS[nIndex]->MUTEX);
 
THREADS[nIndex]->BLOCK = BLOCK;

THREADS[nIndex]->fBlockFound = false;
THREADS[nIndex]->fNewBlock   = false;
}

You can then remove all other places that you are locking accept for the lock in PrimeMiner, which is fine.  As I understand it, you don't need to protect against asynchronous access to integral data types as they are inherently thread safe as they are on the stack, so only protect access to the BLOCK pointer on the miner thread instance.  By doing this, you remove the need for the server thread to have synchronous access to the state of each thread when updating the METERS, so they update regularly rather than having to wait for each miner thread to finish as it is doing now - it mean each METERS read out happens regularly and with consistent results which it is not doing right now.

Unfortunately I'm still seeing the segmentation fault (even with your code) so I think there is somewhere else that needs making threadsafe.

Cheers
Paul

[Videlicet]

Thanks for the data guys, I'll post another update tomorrow; end this bug once and for all. [And get some x64 windows binaries too]

If you are having issues with the Failed to Update Height, try a larger timeout, the default is 10 seconds. This is the 4th commandline argument. 127.0.0.1 9325 4 20. Does it get stuck in a loop of Failed to Update Height, Failed to Connect, etc, or does it eventually reconnect?

I did notice higher PPS on my machine as well. The real tell here though will be SPS, the PPS is prime numbers found per second, SPS is Searches per Second. Prime numbers can be in random clusters, so this is why you see variations with higher PPS and lower PPS each meter update. Searches per Second will tell you how quickly your miner is searching nNonce values, similar to hash rate.

This at least is a decent improvement. We'll see what others can be made. 

Goodnight Everybody,
Viz.

[fudge]

any compiled .exe available?

[Videlicet]

Optimized Miner: I am getting 2 - 3x PPS now [about 40-50 PPS on 4 cores from 18-24 PPS]. We'll see about the Segmentation Faults.

Github Source
Windows x86 [No x64 yet, I still haven't slept]


Had some fun all night with the Sieve of Eratosthenes and Mutexes: some things are more important than sleep! Thank someone for waking me up at 3:00 AM, this and insomnia led me to this update  

Viz.