Quote from: bytemaster on November 13, 2013, 02:23:23 pm

Quote from: donschoe on November 13, 2013, 12:06:23 pm

bytemaster, 15% ... really? If you need this to pay orphans, you should consider another payout system.

I am actively working on a new payout system that accounts for only blocks I find.  It is just as stressful for me when I am losing money left and right.  If we weren't finding blocks every 30 seconds this wouldn't really be an issue.

I have set up a secondary pool, the primary pool is having some trouble with the load:  192.241.139.62

I would appreciate it if some people would switch over to it.   Thanks.

Doing it now

I have concluded that I need to exit the fixed-price per-share market and adopt a model similar to the other pools.   I am looking for someone who would like to run a traditional pool on behalf of Invictus and split the fees.   Please contact me if you would like to set that up.

Quote from: NineLives on November 13, 2013, 05:01:17 am

Even on two inst its the same.  20hpm on one inst 50% CPU, then two inst @ 10hpm each and still 50% cpu.

EDIT:  However, I'm relying on the graph online to show CPU usage.

Run your two instances in tmux or screen.  Then at a normal shell prompt, type top and press enter.

Once top comes up, press the 1 key to see the usage for each processor. My guess is that your using it all.

Quote from: NineLives on November 13, 2013, 04:56:05 am

Down?

I am... or was.. now back..

Quote from: NineLives on November 13, 2013, 12:58:40 am

With or without 8 I'm getting 16.1772hpm  That's not right

I'll try adding 16 to the end or multiple instances

The linux client it should use all of the cores you have available. No need to run multiple instances.

What is the output of (syntax may very a bit by distro):
cat /proc/cpuinfo | grep -c "^processor"
cat /proc/cpuinfo | grep "^model name" | uniq

If I had to guess the 50% is because of the block time (start, stop, start etc). I will check with mine to confirm..

Edit: Hmm a lot of mine are doing the same. Using ~55% of the CPU per thread.

Quote from: NineLives on November 13, 2013, 12:30:44 am

Quote from: flower1024 on November 13, 2013, 12:27:10 am

Quote from: NineLives on November 13, 2013, 12:24:39 am

If i wanted to run multiple instances, do i run putty again and run:  ./coyote_miner 162.243.67.4 [PTS ADDRESS]

i'd suggest installing screen
apt-get install screen

if you start it you'll see a normal shell
use strg+a c to create another
strg+a n to switch between shells
with strag+a d you can detach: you may end putty and your miner continue to work
with screen -r you'll attach again

Problem is, I have 8 cores and one session is only using 50% CPU.  Why?  How can i push it in one instances?  Or do i need to run two?  I don't mind having two puttys for now till I learn more.

run:  ./coyote_miner 162.243.67.4 [PTS ADDRESS] 8
(note the 8 on the end, try that)