spiderdk reputation thread

[spiderdk]

This is my trust thread, here you can post your feedback

[Marsenault]

any reason your rig isnt responding?

[spiderdk]

It is working. I have no issues while mining for myself on the pools i mine.

Are you the person that rented my rig today and was having issues with your pool? Your backup pool worked nice after you added it.

Always add a backup pool and make sure it is working first.

my others rigs are offline as i merged them on one single rig (SPIDERRIG5).

[d3v1an]

Hey,

why do you sell your rig as a 4.4MH/s rig but you only bring 3.6MH/s for the last 17 hours???
http://i60.tinypic.com/2n9m79j.png

[spiderdk]

i had a problem with one of my computers, sorry.

will add you more 5 hours.

[spiderdk]

Your pool reject rate is quite high now, you will get lower hashrate on the average

[x_static]

Your pool reject rate is quite high now, you will get lower hashrate on the average

http://i61.tinypic.com/20qm8u1.png

Code:

sgminer 4.1.0-121-gd480 - Started: [2014-04-23 01:13:28]
--------------------------------------------------------------------------------
(5s):290.8K (avg):292.0Kh/s | A:194576.000  R:16.000  HW:0  WU:269.952/m
ST: 1  SS: 21  NB: 26  LW: 46545  GF: 1  RF: 0
Connected to pool.slackprojects.org (stratum) diff 16 as user M3d00d
Block: 7ea3a507...  Diff:59.2K  Started: [13:14:38]  Best share: 659K
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0:               | 292.1K/292.0Kh/s|A:194576.00 R:0.01% HW:0 WU:269.95/m I:1
GPU 1:               | OFF   / 0.000h/s|A:  0.00 R:0.00% HW:0 WU: 0.00/m I: 0
--------------------------------------------------------------------------------
[13:14:52] Accepted c42fa42f Diff 334/16 GPU 0 at pool.slackprojects.org
[13:14:55] Accepted f96c84ad Diff 262/16 GPU 0 at pool.slackprojects.org
[13:14:57] Accepted 0ac37b64 Diff 23/16 GPU 0 at pool.slackprojects.org
[13:14:58] Accepted 0ff533c4 Diff 16/16 GPU 0 at pool.slackprojects.org
[13:15:02] Accepted 081091ef Diff 31/16 GPU 0 at pool.slackprojects.org
[13:15:05] Accepted 0bf07577 Diff 21/16 GPU 0 at pool.slackprojects.org
[13:15:09] Accepted 02632fd2 Diff 107/16 GPU 0 at pool.slackprojects.org
[13:15:11] Accepted 0a91eafd Diff 24/16 GPU 0 at pool.slackprojects.org
[13:15:12] Accepted 065299ea Diff 40/16 GPU 0 at pool.slackprojects.org
[13:15:18] Accepted 0734cd3b Diff 35/16 GPU 0 at pool.slackprojects.org
[13:15:20] Accepted 0c1b56dd Diff 21/16 GPU 0 at pool.slackprojects.org
[13:15:21] Accepted 65df184e Diff 643/16 GPU 0 at pool.slackprojects.org

Why am I only getting 2.35MH/s @ a quoted 3.10MH/s?  Rig was at 4.95MH/s When I rented...

[spiderdk]

Because your pool is with 16 difficult set as standard. Set it to at lease 128 in order to get more hashrate.

see:

[spiderdk]

My rig was stable on wafflepool earlier from your hire it.

[x_static]

Ok, cool.  I'm new to the whole leasing thing.  Right on for the quick reply.  A+ for that.  I'll see when I can do on my side.

[spiderdk]

Test another pool for 20 min to make sure thats the issue. Search for another pool (mining the coin you are mining now).

Some pools you can set the diff while you create the workers. Check if yours thar can be done.

[x_static]

No other pool for this coin, and the pool doesn't allow for picking difficulty.

I have 4 leased rigs on this coin right now. 

xxxxxxxxx (Scrypt 1.33 MH/s)   1.50   3 hours and 56 minutes   xxxxxxxxx   
SPIDERRIG5 (Scrypt 3.10 MH/s)  2.53   21 hours and 40 minutes   spiderdk
xxxxxxxxx (Scrypt 1.40 MH/s)   1.45   47 hours and 38 minutes   xxxxxxxxx   
xxxxxxxxx (Scrypt 0.35 MH/s)   0.36   47 hours and 18 minutes   xxxxxxxxx   

[spiderdk]

Your pool is somehow not compatible with my system:

You hired 3.1 Mh/s. I am offering 3.2 Mh/s, and you are saying I am offering 2.5 Mh/s. I was using Wafflepool previously and was getting 100% of my hashrate, so its the pool you choose, there is no other explanation. But how the pool configuration varies from yours to mine i am uncertain about it. I still belive its the lower Diff that generates too much request and the LeaseRigProxy cannot process very fast all the information, so It gets delayed and some time are lost on these transactions resulting on a lower hashrate at the end.

[spiderdk]

More info:



See that are 4 requests for new blocks and connections on the same second. Thats the delay and hashrate problem. Using higher Diff will result on large time between requests, loosing less time and increasing hashrate.

[spiderdk]

I see you changed your pool, look:

[x_static]

http://s27.postimg.org/we3mkjhhv/spider5.png

[spiderdk]

Sent you a message explaining the issue. Upgrading my rig and had to be now, sorry. You choose refund or 2x the time.

[RentaMouse]

Had a 25hr hire, found the hashrate to be very variable throughout the day, but average speed was over the 4MH/s promised so not complaining.

Also dont forget to set your worker difficulty at 384 or 512, I got a high reject rate with lower settings.