Definitive Titan Reference Configuration?
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.
Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.
We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.
Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.
We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
-
- Posts: 140
- Joined: Mon Dec 28, 2015 1:58 pm
Re: Definitive Titan Reference Configuration?
With H=5, I seem to have a stable hash rate only 4% less than Nicehash now across my Titans with what appears to be a similar return(moving to par). It had been closer to -10% so this is really good.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Definitive Titan Reference Configuration?
Is Nicehash paying better?excelerator wrote:With H=5, I seem to have a stable hash rate only 4% less than Nicehash now across my Titans with what appears to be a similar return(moving to par). It had been closer to -10% so this is really good.
Try changing h= to a higher value, like h=20, and seeing what that does. I'm guessing that it will show no improvement, which means it should be retained where it is at h=5.
The formula for coin assignment is complicated, but it considers whether a miner will lose more profit in the time during a work restart than would be earned at the higher profitability coin. Therefore, the most profitable coin is not always the best choice for all miners. For miners with high work restart times, like Titans, they can make more money if they are assigned to high-difficulty coins, which is what the server will do unless a low-difficulty coin is so profitable that it makes sense to sacrifice some hashrate to earn a few very profitable shares.
-
- Posts: 140
- Joined: Mon Dec 28, 2015 1:58 pm
Re: Definitive Titan Reference Configuration?
I started yesterday with h=20 but it locked on to LTC and didn't appear to switch. Worked my way back down to h=5 for the current result.
"Is Nicehash paying better" is a little difficult to answer as I can only track results on your site in USD, but given a constant BTC/USD over a two hour period yesterday, with 18 controllers, Prohashing beat Nicehash by ~10%. I know it's a short period, but averaging 18 controllers certainly provides positive directional guidance.
Yesterday I split my controllers across CM, Nicehash and Prohashing so I could monitor the difference.
I'm sending you my addresses for CM & Nicehash so you can do your own math, but I believe we've dialed the Titans in.
"Is Nicehash paying better" is a little difficult to answer as I can only track results on your site in USD, but given a constant BTC/USD over a two hour period yesterday, with 18 controllers, Prohashing beat Nicehash by ~10%. I know it's a short period, but averaging 18 controllers certainly provides positive directional guidance.
Yesterday I split my controllers across CM, Nicehash and Prohashing so I could monitor the difference.
I'm sending you my addresses for CM & Nicehash so you can do your own math, but I believe we've dialed the Titans in.
Re: Definitive Titan Reference Configuration?
d=262144 h=30 appears to be working well with my Titans. Tried some higher d= and lower d= and >100 dropped my hashrate to half and < 30 picks up easier diff coins that appeared to slow hashrate down if I remember correctly.
With d=262144 and h=30 my Titans are switching to other coins like Megacoin, Pesetacoin, Virtacoin, Dotcoin, Gamecredit, Novacoin and Litecoin with no issues. Hash rate as displayed in the Live Worker Status is still shown as half of what is in the miner GUI on some coins and double on others but appears to average out.
Pool rejects are < 1% over 24 hours.
On track to earn a little more here in 24 hours than at Litecoinpool.
With d=262144 and h=30 my Titans are switching to other coins like Megacoin, Pesetacoin, Virtacoin, Dotcoin, Gamecredit, Novacoin and Litecoin with no issues. Hash rate as displayed in the Live Worker Status is still shown as half of what is in the miner GUI on some coins and double on others but appears to average out.
Pool rejects are < 1% over 24 hours.
On track to earn a little more here in 24 hours than at Litecoinpool.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Definitive Titan Reference Configuration?
Unfortunately, I think that for Titans, we may find that the best we can do is to earn just a little bit more. Other miners can earn a lot more than litecoin, but Titans were misleadingly advertised. Instead of calling them "scrypt miners," they should have been labeled "litecoin miners," because they probably decided to cut corners in the design of their chips and knew they would take a long time to restart.gaanthony wrote:d=262144 h=30 appears to be working well with my Titans. Tried some higher d= and lower d= and >100 dropped my hashrate to half and < 30 picks up easier diff coins that appeared to slow hashrate down if I remember correctly.
With d=262144 and h=30 my Titans are switching to other coins like Megacoin, Pesetacoin, Virtacoin, Dotcoin, Gamecredit, Novacoin and Litecoin with no issues. Hash rate as displayed in the Live Worker Status is still shown as half of what is in the miner GUI on some coins and double on others but appears to average out.
Pool rejects are < 1% over 24 hours.
On track to earn a little more here in 24 hours than at Litecoinpool.
Let me know the comparison in profit between the pools today once you get it.
Re: Definitive Titan Reference Configuration?
Won't know today how many licks it takes to get to the center of the Tootsie Roll Pop. Had a power blip while out this evening and just caught it. One of the Titans PSU didn't kick back on so was down one miner for several hours. Will look at what tomorrow brings
Re: Definitive Titan Reference Configuration?
My Titans are Batch 2 with 5 cubes each overclocked to 325Mhz. Each cube has been modified with new fans and individual heat sinks on the DC/DC convertors. They also run GenTarkin's Firmware with BFGminer 5.4.2 and have been tuned with the Energy Saver.
I ran for 24 hours on the 4th with the following settings.
Earnings here today are Wowser!!!. Obviously with the fix of Yobit and some other wallets and a market that is rising I earned for 24 hours
LTC = 13.02741646
If I had mined the past 24 hours at Litecoinpool I would have been in the stats rating around #30 at 9.2 LTC for 24 hours. Closer to 9.8 LTC based on past experience compare to the calculator.
I've turned backed on the love with a 2% tip for Chris.
I ran for 24 hours on the 4th with the following settings.
Code: Select all
{
"pools": [
{
"url": "stratum+tcp://prohashing.com:3333/#xnsub#skipcbcheck",
"user": "username",
"pass": "n=t4 d=131072 h=3"
}
],
"scrypt-n": 10,
"queue": "0",
"scan-time": "1",
"expiry": "1",
"no-longpoll": false,
"expiry-lp": "1",
"skip-security-checks": "0",
"no-unicode": true,
"retries": -1,
"no-submit-stale": false,
"no-show-processors": true,
"failover-only": true,
"quiet": true,
"compact": true,
"net-delay": false
}
LTC = 13.02741646
If I had mined the past 24 hours at Litecoinpool I would have been in the stats rating around #30 at 9.2 LTC for 24 hours. Closer to 9.8 LTC based on past experience compare to the calculator.
I've turned backed on the love with a 2% tip for Chris.
- Chris Sokolowski
- Site Admin
- Posts: 945
- Joined: Wed Aug 27, 2014 12:47 pm
- Location: State College, PA
Re: Definitive Titan Reference Configuration?
Right now YoCoin is in a huge bubble. Its price has doubled overnight, but it seems to be settling down. We're taking advantage of the price spike while we can.
-
- Posts: 140
- Joined: Mon Dec 28, 2015 1:58 pm
Re: Definitive Titan Reference Configuration?
I'm continuing to track performance against Nicehash and Prohashing is still outperforming today by 12% with h=5.
Yocoin has constituted >85% of the $ revenue from the coins I've mined in the last 12 hours.
Yocoin has constituted >85% of the $ revenue from the coins I've mined in the last 12 hours.
Re: Definitive Titan Reference Configuration?
Since the discussion has been on optimizing Titan miners I've looked into other places to optimize: Network that I control and the Raspberry Pi controller.
I run OpenWrt Chaos Calmer 15.05 on my routers. I added Smart Queue Management to OpenWrt on my router following information in this link http://fixmynix.com/openwrt-qos-settings-luci-app-sqm/ and it improved hash rash slightly and smoothed out network performance in/outbound.
Next I looked to the Rasberry Pi. I performed a couple of tweaks with disabling logging, enabling ram disk, and overclocking to medium per steps at this blog http://linuxonflash.blogspot.com/2015/0 ... ry-pi.html.
So far pool rejects are <1% and hash rate seems to be more steady and slightly higher.
Overclocking increases heat load on the Pi and can shorten life without the needed cooling or heat sinks.
Will see what long term running brings.
Proceed at your own risk.
I run OpenWrt Chaos Calmer 15.05 on my routers. I added Smart Queue Management to OpenWrt on my router following information in this link http://fixmynix.com/openwrt-qos-settings-luci-app-sqm/ and it improved hash rash slightly and smoothed out network performance in/outbound.
Next I looked to the Rasberry Pi. I performed a couple of tweaks with disabling logging, enabling ram disk, and overclocking to medium per steps at this blog http://linuxonflash.blogspot.com/2015/0 ... ry-pi.html.
So far pool rejects are <1% and hash rate seems to be more steady and slightly higher.
Overclocking increases heat load on the Pi and can shorten life without the needed cooling or heat sinks.
Will see what long term running brings.
Proceed at your own risk.