Crypto-Expert / stratum-mining

AIO Stratum mining server for various coins
Other
365 stars 348 forks source link

Need an advice #271

Closed ghost closed 10 years ago

ghost commented 10 years ago

Hi! I orderd new server with these specifications : CPU - 2x IntelXeon 6core 3ghz Ram - 64GB ECC 1333mhz HDD - 4 x SSD Raid 1 Connectivity is very fast, im just curious what are the best settings for stratum-mining runnin on this server ? i will ran max 15 coins half sha256, half scrypt can you help me?

cryptoharvester commented 10 years ago

What stratum settings are you interested in changing?

On Sunday, February 23, 2014, eskal notifications@github.com wrote:

Hi! I orderd new server with these specifications : CPU - 2x IntelXeon 6core 3ghz Ram - 64GB ECC 1333mhz HDD - 4 x SSD Raid 1 Connectivity is very fast, im just curious what are the best settings for stratum-mining runnin on this server ? i will ran max 15 coins half sha256, half scrypt can you help me?

Reply to this email directly or view it on GitHubhttps://github.com/Crypto-Expert/stratum-mining/issues/271 .

ghost commented 10 years ago

these settings :

Don't change these unless you know what you are doing

DB_LOADER_CHECKTIME = 15 # How often we check to see if we should run the loader DB_LOADER_REC_MIN = 10 # Min Records before the bulk loader fires DB_LOADER_REC_MAX = 50 # Max Records the bulk loader will commit at a time DB_LOADER_FORCE_TIME = 300 # How often the cache should be flushed into the DB regardless of size. DB_STATS_AVG_TIME = 300 # When using the DATABASE_EXTEND option, average speed over X sec

Note: this is also how often it updates

DB_USERCACHE_TIME = 600 # How long the usercache is good for before we refresh

**** Pool Settings *****

User Auth Options

USERS_AUTOADD = False # Automatically add users to database when they connect.

This basically disables User Auth for the pool.

USERS_CHECK_PASSWORD = False # Check the workers password? (Many pools don't)

Transaction Settings

COINBASE_EXTRAS = '/stratumPool/' # Extra Descriptive String to incorporate in solved blocks ALLOW_NONLOCAL_WALLET = False # Allow valid, but NON-Local wallet's

Coin Daemon communication polling settings (In Seconds)

PREVHASH_REFRESH_INTERVAL = 5 # How often to check for new Blocks

If using the blocknotify script (recommended) set = to MERKLE_REFRESH_INTERVAL

                            #   (No reason to poll if we're getting pushed notifications)

MERKLE_REFRESH_INTERVAL = 60 # How often check memorypool

This effectively resets the template and incorporates new transactions.

                            #   This should be "slow"

INSTANCE_ID = 31 # Used for extranonce and needs to be 0-31

**** Pool Difficulty Settings *****

VDIFF_X2_TYPE = True # Powers of 2 e.g. 2,4,8,16,32,64,128,256,512,1024 VDIFF_FLOAT = False # Use float difficulty

Pool Target (Base Difficulty)

POOL_TARGET = 32 # Pool-wide difficulty target int >= 1

Variable Difficulty Enable

VARIABLE_DIFF = True # Master variable difficulty enable

Variable diff tuning variables

VARDIFF will start at the POOL_TARGET. It can go as low as the VDIFF_MIN and as high as min(VDIFF_MAX or coindaemons difficulty)

USE_COINDAEMON_DIFF = False # Set the maximum difficulty to the coindaemon difficulty. DIFF_UPDATE_FREQUENCY = 86400 # Update the coindaemon difficulty once a day for the VARDIFF maximum VDIFF_MIN_TARGET = 16 # Minimum target difficulty VDIFF_MAX_TARGET = 1024 # Maximum target difficulty VDIFF_TARGET_TIME = 15 # Target time per share (i.e. try to get 1 share per this many seconds) VDIFF_RETARGET_TIME = 120 # Check to see if we should retarget this often VDIFF_VARIANCE_PERCENT = 30 # Allow average time to very this % from target without retarget

i was always running on defaults, only changed diff settings. But now I have this fast server so Im curious about the other settings, thanks

ahmedbodi commented 10 years ago

DB_LOADER_CHECKTIME = 15 DB_LOADER_REC_MIN = 10 DB_LOADER_REC_MAX = 50

^ Increase these

moszis commented 10 years ago

Ahmed,

Sorry to respond to this after you already closed the issue.. but you have touched on the subject I have long wondered about.

While I understand what those settings do and exactly the changes it would propagate, I'm having hard time correlating your suggestion to having "bigger" server. Why is it going to improve performance to write more records at a time with longer wait in between? I was worried that its going to create bottlenecks in the database... Or are you making this suggestion on the fact that OP is planning to run 15 coins on the same server?

Thank you very much!

ghost commented 10 years ago

yes im very curious about these settings, my server can run too many operations at a time... disks are so fast and also CPU has 24 threads... so it is counting very fast...

ahmedbodi commented 10 years ago

my bad I should have explained it (was in college). but here goes DB_LOADER_CHECKTIME should be low (how often it checks if It can insert shares) DB_LOADER_MAX should be high so it submits a large amount of shares to the db DB_LOADER_MIN should be low so that even at low loads it will still insert all the shares rather than queueing them unnecessarily

ahmedbodi commented 10 years ago

From experience I can definitely say the db is the bottleneck in stratum. if someone replaces the code to be asynchorous. everyone will get a major performance boost.

moszis commented 10 years ago

Fantastic! That makes perfect sense. Thank you.