Topic: [POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com - page 153. (Read 465716 times)

Just an interesting graph on dogecoin since the fork by pminer:

http://i.imgur.com/mXR2976.png

The DLf7 address was a big random block reward abuser before the fork with high volume, now they're mining it a lot less and only very selectively. Not sure who they are..

Wafflepool

I am new to mining, howeever I am good at building the machines and getting them started. This is where my knowledge falls off, any chance you could put some information on your site on how to fine tune the machines or WE could pay someone who is mining on your pool to put up the information for us on how to fine tune our machines for your pool specifically. I would greatly appreciate the help.

Thanks

The instructions are good, but are solely for terminal based Linux installs. Below are the instructions for BAMT 1.5: I run everything off of a USB thumbdrive

Note: I highly recommend using Pastebin and copying/pasting these instructions along with your favorite CGMiner config. BAMT comes with Iceweasel browser, and from Pastebin you can copy/paste the apt-get and git clone commands into BAMT, as well as copy/paste your cfg file.

1. Shut down all mining processes via BAMT Start Menu > BAMT Control > Stop Mining Sessions
2. Open Terminal via BAMT Start Menu > Accessories > Root Terminal
3. In terminal, type the following and then hit enter: sudo apt-get install libcurl4-openssl-dev pkg-config libtool libncurses5-dev libudev-dev
4. Go to BAMT Start Menu > Accessories > File Manager
5. In File Manager, click the "OPT" shortcut on the left-hand column, and then open the "miners" folder.
6. Right click and rename the "cgminer" folder to "cgminer.old"
7. Right click empty space, and create a New > Folder , naming it "cgminer" (without quotes)
8. Back in your terminal window, type the following and hit enter: cd /opt/miners/cgminer
9. In terminal, type the following and hit enter: git clone https://github.com/Kalroth/cgminer-3.7.2-kalroth
10. Back in File Manager, open the "cgminer" folder, and then open the "cgminer3.7.2-kalroth" folder.
11. Select all the files (CTRL+A), then Cut the files (CTRL+X)
12. Take a step back to the "cgminer" folder, and Paste the files (CTRL+V)
13. Take another step back into the "miners" folder, and then open the "cgminer.old" folder
14. From the "cgminer.old", open the "APL_SDK" folder
15. Select all the files in this folder, and Cut or Copy them (CTRL+X for cut, CTRL+C for copy)
16. Head back into your "cgminer" folder (/opt/miners/cgminer), and open the APL_SDK folder here
17. Paste (CTRL+V) the files you copied from the "cgminer.old/APL_SDK" folder into this one
18. Go back to the Terminal window, then type the following and press enter: ./autogen.sh --enable-scrypt --enable-opencl
19. Once the process is completed, in the terminal window, type and press enter: make
20. The miner has now been setup. You can alter your config file by going File Manager > bamt (shortcut in left hand side colum) > Then double-click the cgminer.conf file
21. Once everything is setup, go to BAMT Start Menu > BAMT Control > Restart mining sessions
22. If you want to view the typical CGMiner window, open up terminal and type: screen -r    (Keep using the command until CGMiner shows up)

Actually had nothing to do with the doge recompile (although it did fix that bug - it was only a visual bug).

What actually happened is:
At some point while growing (not the last week, but when we were up at like 35GHs), we were selling enough coins (dogecoin, others as well), that when we would sell a large batch (if cryptsy's wallet was slow to process our deposits, we'd have a ton to sell, or we just found multiple fast large blocks), we would put in one sell request (call it 2mil doge), and cryptsy would match it with other buy requests, and the trade would complete in many different parts.

Since those different parts could potentially be at different prices, the way we handled figuring out sale price was by going through the recent trades list from cryptsy (which has the actual price listed).  We would pull the most recent 200 trades we made, and get the actual price, and process then.  Turns out, some of the trades we made, actually came back in more than 200 pieces.  So we'd end up processing the vast majority of them (200 / 210 or something), and that last bit would be left (never seen on our side).

The fix was to just have a script pull literally every trade we've ever made on cryptsy's side, and re-process them all.  Essentially those coins that were listed as "unexchanged" had been exchanged previously, just never credited to user accounts.  I went through and did it for all our coins, so everything should be 100% sync'd up.  Quite a nice "check everything lines up" script.  I'll be running it every now and then

Can't really blame you for not wanting to share your knowledge. Are you really recommending bitcointalk as a good source for learning the finer details of mining?

Yeah.  I had suspected it had to do with our loadbalancer (haproxy).  We switched to a different method with the new stratum server, so we're not going through that anymore

Just for the sake of correctness, xintensity was written by ArGee from RGminer, then imported to kalroths fork of cgminer and then to sgminer (see https://github.com/veox/sgminer/commit/7aeae40af22e6108aab8b68a229eea25a639d650). I use sgminer and believe it is the better option.

I see the unconverted has dropped with the dogecoind recompile which is nice. Profitability is also looking great for the day, and we're mining a more even spread of coins. It'll be interesting to see how the other pools do for the sake of comparison. Thanks for the work poolwaffle.

Thanks, gonna make the switch

I run Kalroth's fork in BAMT with no issues. Three separate R270 rigs.

*Edit*
Here's the guide: http://www.reddit.com/r/dogemining/comments/1xz1x1/how_to_setup_kalroths_fork_of_cgminer_cgminer373/

Kalroth came first as veox mentions taking some functionality from that branch in their work.  I think one of the advantages of sgminer is that development is continuing whereas cgminer has left scrypt behind.

Several features, including the xintensity first came in kalroth, it is better looking, more and better detailed too, but it lacks linux support. On win boxes I'm always kalroth

Kalroth cgminer does as well

Dunno if anyone else have noticed, but somehow server update seem to get rid of that getwork issue. For a half day not a single getwork failures. Pretty dramatic improvement! From tenths to zero, as merely a side effect.. pretty nice.  

Still seems something happen time to time to the connection, as there's couple occasional reconnects in a day. Well, better than dozen getwork failures in a hour I suppose.  

Ping is around 50-60 in a EU.

All we are missing now is altcoins with a actual value.  

Could you share with us some of the finer details for optimizing hash rate / work usable / power consumption? I agree this thread is not the place for such discussions, that's why I'm only asking if you could direct us to some web resources.

your android app is so brilliantly made that after the update from 18th I uninstalled it. Kudos to you.

I think doge had a little fork after 1.6 update.
Also i think cryptsy has problem with doge deposit's now.

Don't think thats it, I think theres a daemon problem.  Specifically I'm seeing these: https://github.com/dogecoin/dogecoin/issues/341 show up in our send logs.  I'm guessing that has something to do with it.  Going to be upgrading the wallet right now, and rescanning/indexing.  Dogecoin mining will be down for a bit here (not sure how long this takes).

They've upped the block confirmation time with the new 1.6 fork. It now takes 240 confirmations which is around 4 hours (previously it was around 30 minutes).

So I'm looking into why we have so much unexchanged dogecoin.  At first glance, nothing is wrong on our side... Confirmed our sends are getting to the exchange, confirmed our trader is trading them for BTC, and confirmed our scripts are processing the trades correctly.  Everything looks fine.

On second glance, our dogecoin balance (locally on our coindaemon) says 0 balance, and on dogechain, says we have a decent amount of unspent coins at our address...  Going to check to see if maybe something got confused/missed when we were upgrading the wallet...

1. You need sgminer for that. I'm not a linux expert, called for help a friend that installed sgminer 4.1.0 on the rigs, didn't look all that complicated, but what do I know xi is based on shaders on the card, and there are odd times that it actually has the same value as I - for example on 280x/7950 I13 is perfect as it is hitting right on the shader count.

2. Yeah that is the theory - you should be using ever bit of speed on the card to get to work. The practice, however, differs. The programming on these cards is quite complex and often what seems logical results in illogical results, not sure if it is because of the way code is written, or optimizations, you can have the card working to the booth and still don't produce as fast results as a setting that is much more relaxed and can have the card with power to spare, including allowing you to watch movies (hashrate drops some 5-8% when watching movies tho). I totally agree that the aim should be best results for given clock/temp/consumption, so what I try to optimize is to find the most relaxed settings that give me the same/better efficiency than the commonly used ones. For example 280x the commonly used one is good enough, not the case with 7950, and to a degree - 290

I heard another explanation about intensity - it is internally how much processes are running, so upping it results in taking on many tasks, but every single one is completed slower - not that much of a problem with slow coins, but on fast blocks using higher intensity you are not giving it a chance to complete and submit the job, so the general advice on shitcoin mining is to find a low intensity that does the job good enough.