Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Entz

Pages: [1]
1
How does he know what addresses to send payments to?
that is a good question. I would assume that he will re-enable logins and users can withdrawl them (fee free!) to whatever account they choose.

2
General Discussion / Re: Coinground Alpha PTS Exchange - trading back up!
« on: November 15, 2013, 08:50:32 pm »
Agreed, the exchange works great! Good job.


3
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 13, 2013, 05:43:01 am »
And it will :)    I have solid intelligence that a top 3 BTC exchange will be listing PTS within a week.   Note: we did not partner with them... they are doing this on their own initiative.

Good news indeed :D

4
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 13, 2013, 05:39:13 am »
At the command line run:
top , then press 1 to see the cpu usage per processor (first column)

Alternatively you can install htop, which is a nicer version (imo). To do that you would need :
sudo apt-get install htop
htop

All of the coyote_miner processes should be at the top, with the first line being the total of all and the rest being the individual threads. I like to hit F5 for the tree view.

Now unless you changed the number of threads it uses, it should be using all of them. Though as mentioned above it seems to need more than one instance per 8 threads..

5
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 13, 2013, 05:07:04 am »
Either top or ideally htop (break down by thread)

6
BitShares PTS / Re: Coyote Miner | PPS Mining Pool
« on: November 13, 2013, 04:16:26 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.

Pages: [1]