Topic: ### A ChainWorks Industries (CWI) Project - CWIgm | Simple Powerful Stable - page 17. (Read 67732 times)

Correct me if I'm wrong, but orphans still give 1250 coins per block. So I don't see the big deal.

on a completely unrelated topic from my post above.....


something is up with orphans. 

4 in the last 24 hours seems high when the total for the last week is 7, and "lifetime" (yes i know the pool is young) is 10.

that means that 40 percent of orphans came in the last 24 hours, which seems abnormal.

edit:

just checked suprnova, and they're showing 1 orphan in the last 24 hours and 6 in the last week.  they also found a tenfold or so more blocks in that period, so they technically should have many more orphans, not less.

so yeah, something is up with the orphans.

your hashrate in the miner and the pool will always vary a bit, that's not abnormal.

it's much more pronounced with this miner/pool combo, though.  the pool tends to jack up worker diff way too high, and this makes smaller rigs choke up.

for example, as i'm typing this, all of my rigs are shown to be set at 248 diff by the pool.  my x6gpu rig has zero issues handling it, and is humming right along.  however, my x2 and x1 rigs are struggling to submit work consistently.

and that's what you're seeing at the pool - inconsistency.  smaller rigs just don't get the time they need to submit shares at this high difficulty.  you can easily see that when you look at the miner window for smaller rigs - if you see a lot of "mean netdiff" and not a lot of "share", then your card is choking and is not submitting shares consistently.

this is why you're seeing wild fluctuations in hashrate with smaller rigs at the pool.   they are working at a very high worker diff, so when blocks are fast they simply do not have the time they need to finish their calculations and submit a share before a block is found.  this is why you will occasionally see them appear to drop off from the pool.  they didn't really drop off, they just didn't submit any shares in the x amount of time the pool uses to calculate your hashrate.  so let's say it takes 60 seconds for the pool to update your worker hashrate, and in that minute your rig didn't submit any shares - it will appear to drop off from the pool.  reverse that for when the blocks are slow - smaller rigs get enough time to breathe and start submitting shares.  because of the high worker diff, they are submitting large shares.  when that happens you will see your hashrate go up wildly.  for example, it's not unusual for me to see one of my x1 1070 rigs appear to drop off the pool, and then reappear with the hashrate of 90-120mh (3x4 it's normal sigt speed) a minute later.

like i said, all my rigs right now are set by the pool to mine at worker diff of 248.  x6 rig has plenty of power to consistently submit shares, and its hashrate at the pool is consistent.  it does fluctuate a bit here and there, but it's close to what it's supposed to be.  my x2gpu rig has a harder time keeping up with this diff and is wild.  my x1's are just all over the place, sometimes disappearing from pool for long stretches (didn't submit any shares) and then reappearing at 3 to 4x their hashrate.

this isn't a new thing, and has been brought in this thread - so the devs are aware that this is happening. 

not sure if there is a fix coming, or they plan to leave it this way, but since i started mining here this has been my one and only problem with this miner/pool combo - i am literally happy with everything, except this

well for me is the same, the hasrate is not stable

Damnnn! Thanks broski. I'll try it out!

im mining sigt too. same things are occurring. 

Anybody explain to me what is ORPHANED on trasactions? Only see from today

lol I thought u're talking about sigt pool

nope, pretty sure im in the right pool. sometimes the worker is there, sometimes its not whenever i check.

and the hashrate is not same with what my miner says. im using gtx 1070 for denarius mining and my miner always show around 53mh hashrate, the dashboard randomly range from 27 to 130, or 0 when the worker went inactive.

What is ORPHANED on trasactions?

ok, if you want just close miner app, use external batch file.

for get temp use nvidia-smi.exe --id=0 --query-gpu=temperature.gpu --format=csv,noheader,nounits , where --id=0 - you GPU


like as (for 6 GPUs)

for /F %%p in ('"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" --id^=0 --query-gpu^=temperature.gpu --format^=csv^,noheader^,nounits') do set gpu_temp0=%%p
for /F %%p in ('"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" --id^=1 --query-gpu^=temperature.gpu --format^=csv^,noheader^,nounits') do set gpu_temp1=%%p
for /F %%p in ('"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" --id^=2 --query-gpu^=temperature.gpu --format^=csv^,noheader^,nounits') do set gpu_temp2=%%p
for /F %%p in ('"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" --id^=3 --query-gpu^=temperature.gpu --format^=csv^,noheader^,nounits') do set gpu_temp3=%%p
for /F %%p in ('"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" --id^=4 --query-gpu^=temperature.gpu --format^=csv^,noheader^,nounits') do set gpu_temp4=%%p
for /F %%p in ('"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" --id^=5 --query-gpu^=temperature.gpu --format^=csv^,noheader^,nounits') do set gpu_temp5=%%p
set /a total=%gpu_temp0%+%gpu_temp1%+%gpu_temp2%+%gpu_temp3%+%gpu_temp4%+%gpu_temp5%
set /a gpu_tempaverage=%total%/6

if %gpu_tempaverage% GTR 70 (
   TASKKILL /IM cwigm.exe
)

this is a dumb question but yor are cheking your coin dashboard? because there is a loot of coins on the pool, make sure you are on the rigth coin it happensd to me xD

Hi, can you please PM with the details? I have been mining to your pool using a different miner, but wouldn't mind testing out CWIgm!

yep cant access dashboard,
but am still receiving shares

my miner seems to be working fine but on my dashboard, the worker is not active. therefore my hashrate is 0 

but i still getting my coins. is it a bug?

all good ...

and no ... i shall be very blunt with this question when it arises - as with all the questions like this that have been asked too many times now ...

if there is news - you can rest assured it will be published ... no news means we are still working in the background and on the backend ... we will NOT hype - just produce ... thats why our focus is not on anything else but our projects ...

...

#crysx

My bad - I was referring to sigt pool. Since last time the miner has been stable for the last 12 hours or so.

do you have eta on the new miner?
thanks

which pool? ...

you ask as if we only have one pool ...

i have been doing maintenance - yes ... some of the maintenance does not involve the stratum - others do ... its a short 25second interval between stratum drop and uptime - so its a very small effect on the uptime of the pool ... however - there have been attacks on a regular basis - and we know which ips they are coming from which tends make me believe that some 'badboys' may be commissioned to do some stuffing around with ddos and hacking ... if this is the case - we have a legal issue on our hands - and will fight it to the end ...

either way - we will continue to improve the security AND stability of the pools as well as CWIgm ...

testing the sweep pool very shortly - so will have a bit of downtime on that pool also ... DO NOT mine on that pool please unless you are willing to test the pool ... this means you will probably LOSE your hashrate to the pool for testing purposes ... CWI-Pool SweepStakeCoin is in alpha - and is being tested internally ... will go to beta designation when we have finished with internal testing for public testing / use ...

#crysx

these points are all true - depending on what your configuration of the cards are - miner - and os ...

mess around with the settings of all three and see what you get ...

there is no ONE way to do it - as each machine ( computer ) is unique and have different settings ... from bios to software settings ...

#crysx

no no no ...

you are not wasting our time - or 'dumb' - or bothering us ...

but it seems you misunderstood WHY we were explaining what we have been ... there is NO option in the current miner ( or any other miner ) to do what you ask - unless an external application takes these values and uses them to determine what to do with CWIgm running ...

tell you what tho - if this is something a few users CAN use - lets see what can be done ... this IS a beta afterall - so testing new things wont hurt ... depending on how mcuh work we need to put into the coding of it of course - as other things take priority for the time being ...

much appreciated for the positive and kind words also ...

#crysx