also depends on the card.  i currently have three different model cards that i mine with.  they all seem to be tuned differently in terms of tdp right from the factory.  for example the asus and msi cards i have both have wacky tdp, with msi running 20 watts higher right off the bat, and asus running about 10 watt lower then a "standard" founders edition cards.  my evga cards are a completely different story.  they most reflect the power settings of the fe cards, and have the best power management out of all of them.

in other words, it doesn't just depend on the model, but also how the maker tunes the cards at the factory, and they all have their own sweet spot.

for example.

msi 1070 - 135w at 65 tdp, if i go any lower the hash drops about 20 percent instantly.
asus 170 - 125w at 75 tdp, any lower and the hash drops by about 20 percent.
evga 1070ftw - 110w at 60 tdp - can go lower on wattage (down to 50%tdp) while dropping the hash proportionally, after 50 the hash drops significantly.

all produce about the same hash rate at these power settings - 53-54 on dnr, with asus lagging behind at about 50.

i found the evga cards to be much better in adjusting power, and overall most flexible.  msi to be a bit faster closer full tdp, and asus pretty much terrible at everything.  the only saving grace for the asus is that it only requires a single 8 port pin, which would make it easier to deploy at scale. the evga requires a dual 8 pin power plug, which is a pain in the ass to find cables/adapters for, especially when you need to run 6-8 of them on a single rig etc..   i got the msi and asus cards first, then i got the evga's... i've been getting nothing but evga since.

[08:06:33]Mean netDiff: 18283.5
[08:06:53]Mean netDiff: 18204.3
[08:07:03]Mean netDiff: 18153.6
[08:07:43]Mean netDiff: 17965.8
[08:08:33]Mean netDiff: 17896
[08:08:59]Share: 23200d2c
[08:09:23]Mean netDiff: 17871.6
[08:09:33]Mean netDiff: 17884

looks like the worker diff is still being jacked up a bit too high.  this is from an x2 1070 rig.  pool currently has it at diff 409.6 (same exact diff as a x6 gpu rig), which is a bit too high (128 would be ideal, with 256 still ok but pushing it).

with this diff, the rig was only able to submit one share in the last 7 blocks.  it's actually more then 7.  the miner window only has so many lines, and there are at least a couple of blocks that already scrolled out of view, so it's closer to 8-9 blocks.

so this 2xgpu rig only contributed to finding one out of the last 8-9 blocks.

this is what i meant by gpu's being chocked by high worker diff.

it's rare for any pool to show your hash that precisely all the time.  

hashrate reported by the pool will always fluctuate.  when you mine coins with fast blocks (like sigt or dnr), it will often fluctuate wildly.

keep in mind, the pool doesn't know or care about your actual hashrate.  it can only count the hash by the shares you actually submit.  when blocks move fast, your gpu will sometimes submit a lot of shares, and sometime will not be able to submit any before a new block is already in play.

for example, my single 1070 that mines at 29'ish sometimes shows up at 50 and sometimes shows up at 10 etc.

all depends how many shares it managed to submit in whatever polling period the pool uses to measure hash.

yeah, i figured you guys were playing with the stratum to update something or other, which is why i mentioned in in a ps.  not a big deal.

i really like this approach of the same people working on both the miner and the stratum to ensure that both of them can play together as nice as possible.  it does create a closed ecosystem, which typically is not a great thing, but in this case i don't really mind.  i'd rather have an efficient closed ecosystem that is run by people who know their shit, then a hosh posh of open solutions that don't play well together.

like i said, great job so far.

now let's see what you come up with next - no pressure

i run my 1070's at 60tdp.  

much like overclocking a cpu, there comes a point of diminishing returns, where you pump up extra power and heat for very little return.

in the case of my gpu's, i found that i can mine dnr at 58 at 100tdp, or 53-54 at 60tdp (110w).  the difference in hash is under 10 percent, the difference in power is over 50 watts, or just over a third.

but it's not just for the electricity savings.  with less power comes less heat - my cards pretty much never go above 60C.  i'm looking at my x6 rig now, and the hottest card is 58c.  this also means less worries about cooling the room the miners are in.  less heat produced - less ac needed to cool the room ec.

and less power also means i can run the entire x6 rig off just one 1000w power supply.  the entire rig only draws just over 700 w from the wall., according to a power meter.  this means that i can add more rigs to a circuit without overloading it, and can easily run 3x6 rigs on a single 20 amp line.  i would not be able to do that at full tdp.

point is - while not for everyone, there are many advantages (beyond just saving on cost of electric) to running at lower tdp.

running for well over 24 hours now.

speeds are same as in my last report (29 and change per 1070 - 125/500/60tdp).  everything has been stable, with no crashes and no other wacky behavior.

last night worker diff was still set too high, leaving my single and x2 gpu choking.  a diff of 256 is just waaaaay too high for a single gpu

that said, i checked this morning, and it looks to have already been fixed.  at this moment my single gpu rigs run at diff 64, which through my personal experimenting on both yiimp and nova looks to be the sweetspot for a single 1070.  the x2 rig runs at 128 etc. excellent.

my x6 rig however is set at 258, which is just a tad too low.  ideally, i would love to see it at 384 (6x64).

overall, very impressed so far.  the high worker diff issue was brought up yesterday, and is already fixed.  miner runs great, pool keeps finding blocks, and everything is working as it should... so all, good.

great job, guys.

ps... looks like the pool was down for a bit this morning, since i see a bunch of "failed to connect, retrying in 30 seconds" lines in the miner.

i'm not the dev, so he'll give you a better answer.

But i did play with DNR miner, and i noticed that it has a condition in the bat file that pauses the miner when the netdiff gets high.  When the condition is met, the gpu idles for a few blocks, no shares are submitted etc.

I took --mean-net-diff=1.1 out of the bat, and that behavior stopped.  I'm guessing that most people leave that in, so all (or most) of the miners pause for a few blocks here and there, which adds to the time it officially takes the pool ti fond a block, which screws up with the already wacky luck calculation on DNR.

I have a feeling that if everyone changed their bat file, the luck would improve drastically.

if you get your hands on win10 ltsb it will never update.  It will still get security patches, but no updates to knock out the activator.

6 and change btc's worth of sigt...

yeah, the dev selling is really going to crash the coin

Trying a single 1070 gpu (+125core/+500mem/60%tdp) with denarius (tribus) on win7.

Immediately noticed a new command in the bat that doesn't exist in the bat for sigt  --mean-net-diff=1.1

Miner reports a speed of 53.  I have never mined this algo before, so nothing to personally compare it to, but i did check yiimp benchs- 53 is pretty damn good

After a few minutes i noticed something weird.  In the right bottom box, a yellow line saying net diff > mean net diff.  The netdiff field in the miner turned red, and the miner just stopped mining.  I could see the card idling in afterburner.  This went on for a few blocks, then the netdiff field turned green, and the miner resumed.   Rinse/repeat every 5-10 minutes or so, with each break lasting about 2-3 blocks.

I guessed that the --mean-net-diff=1.1 was causing this, took it out, and this behavior stopped.  Miner just kept on mining.

I'm not sure what --mean-net-diff=1.1 is meant to do, and it's probably there for a good reason. For me, however, it's pausing the miner and makes the gpu just sit there idling for a bit.  An idling mining gpu is a sin

even if he completely bailed out, his would be 1/70th of the volume of today's trading.  not sure if it's enough to trigger such a massive crash.

most likely, it was caused by people taking their profits from idiots who were screaming "to the moon" all over the place.

with no pre-mine, meaning no free coin for the dev, chances are he acquired his the same way everyone else has - mined them, or bought them.  he also has a right to sell, some or all of it, if he wishes - just like everyone else.

so, this means nothing... at least to me.

At the moment - you're a bagholder.  And as a bagholder you have two options, take your losses or keep holding the bag until the next round of bagholders bails you out.

There is another halvening coming up about 3-4 weeks from now, and in another 3-4 weeks comes POS.  It is not definite, but at least likely, that this coin will see at least another big pump right before one of those two events, maybe both.  

ok, some quick observations after running for about 8 hours or so.

Short version - miner reports great hashrate, better then any other i tried so far.  However, the pool likes to jack up the worker diff way too high, choking out smaller rigs.

Long version:

Trying on a total of 10x1070's spread across one main rig, and some random boxes.

box 1 - win 7, single gpu. (worker 1)
box 2 - win 10, single gpu. (worker 4)
box 3 - win 7 2xgpu (worker 2)
box 4 - win 10 6xgpu. (worker 3)

All gpu's are tuned with exactly the same settings - +125 core, +500 mem, 60%tdp (110w) in afterburner. These were my go to settings for zcash and lbry, so i left them alone for now  All get just over 29mh on skunk, according to the miner.

However, and this is especially true for the single and 2x gpu machines, the pool difficulty ends up being too high.  The single gpu's started out at pool diff of 64 (worker at 0.25), which from my previous experimenting is the sweet spot for a single 1070 gpu, and then eventually ended up at diff of 256 (worker at 1).  At 256 the card chokes.  When the nethash is nice and steady, the card is still able to submit work ever 2-3 sometimes 4 blocks.  When whatever is hitting this coin hits it hard (when you see the nethash double in like 5 minutes) the card can't keep up with fast moving blocks at all.  There was a time when i caught a glimpse at the miner and saw at least a good dozen blocks go by before the card was able to submit any work.  There were instance that the card was so chocked, the pool would show that a worker dropped out, meaning that the card submitted no shares in whatever time interval the pool uses to calculate hash.    In fact, as i'm typing this i can see the miner window on my single gpu boxes, and one of them just had about 10 blocks go by without any work submitted (diff 256 pool, 1 at worker).

It's a similar story for the 2xgpu box.  The diff started off at 128, which again i think is a sweetspot for this setup, but then climbed to 512.  At that diff, just like the single gpu setup, too many blocks go by before a share is submitted and the cards choke.

6xgpu rig seems to be not as affected by this.  It started off at 256, then eventually climbed to 640.  It too misses out on blocks, and hashrate reported at the pool jumps around wildly, but at least it's able to get some shares in every other block or so.

Overall, i am very happy with the miner.  The pool is finding blocks at a good clip, and with good efficiency, so maybe this approach of jacking up the worker diff works.  But it feels wrong to see this many bunches of blocks go by without a share submitted.  To me it means that my gpu's are not even competing to find a solution to a whole lot of blocks.  You can't solve a block if you don't at least compete to solve it.

As i was finishing typing this, another 6 blocks went by before my single gpu rig submitted a share.  That means that this particular gpu didn't even compete for 6/7th of the opportunities to find a block.

just tried this.

win 10 didn't throw up any flags, so i guess it's clean.

i get the same speed as spmod on my 1070s at 60%tdp (my sweet spot setting for these cards) - 28.

not sure if it's this compile or the coin's network that's being hammered, or the miner overall,  but it was very slow to start submitting shares.  took well over a minute on yimp before i saw a white line, and almost two on nova.

that sucks... that means that whatever is cannibalizing the other nvidia coins has found this one as well.  it's not getting hit as hard as lbry and zcash, but its getting hit. 

which i guess would explain the wild diff jumps/retargeting.

is the nethash displayed correct ?  i see it yo-yo from 1.5 to 3.5 th in a matter of minutes.  

is it being hit by something heavy everytime the diff dips like other nvidia coins ala lbry (just went from 7 Th to 29 Th nethash, and diff of 270 to 1100 in a matter of 10 minutes) ?  

i'd like to give this beta a try...

pm sent.

in theory, it should matter... in theory.

i checked last night, and nova was 3 times as large as all the other pools combined.  this means that to have "perfect" 100 luck, nova needs to find 3 out of every 4 blocks.   last night when i checked nova found like 800+ blocks, and was still running 110-120% luck.  a smaller pool like - http://pool.chainworksindustries.com/sigt/index.php?page=statistics&action=blocks - only needs to find 13 blocks during that same time to have close to 100 percent luck.  if they find 14, they're in the plus.

so in theory, a smaller pool should be able to average out better when these "hits" of hash rate come in because it doesn't have to find almost every block to stay in the plus... but again, that's just theory.

kind of sort of yes... it's more like network overload.

the nethash doubles, and sometimes even triples in a matter of seconds, and this lasts for only a few minutes.  if you look at your miner as it's happening you'll see blocks being found super fast, like back to back to back.  if you see three or 4 green lines in a row before you see a white line,  it means that your miner is getting work, but is not able to submit shares because the block is already found.  the pool can only credit you for the hash you submit, so during those times the hash suffers.

every time the diff drops to teens or low 20's, the nethash doubles.  some big pool is hitting the coin when the diff is low, mines until the diff skyrockets back up. rinse/repeat.