If my node is configured with 1mbit blockmaxsize and minrelaytxfee=0.00001 latency is 0.4-0.9s. That makes miners go allmost asleep - i dont get much shares with these settings alltough it doesnt affect efficiency rate.
blockmaxsize=100 000 minrelaytxfee=0.0005 latency is +-0.03 and butterflylabs sc:s start to make noise.
Changing these settings doesn't affect the share rate whatsoever.
Well I can say that youre wrong, very much indeed. Going from 0.03s to 0.4s latency you will see alot less shares with asics, because of the lag ofcourse. Immediately you can hear the difference when your equipment runs with work all the time, fans start to really blow..
Try it, and tell us how it went.
one week with 1000 000 blocksize and 0.0001 fees, then the next week drop it to 50 000 and 0.005 fees. If it doesnt make you more shares then the first week im suprised.
But if you have bitcoind on ramdisk difference might not be that big then, im going to try that when my memorys arrive.
Theres one thing if you run your node on linux kernel that can be tweaked too, infact two
Preemptible Kernel (Low-Latency Desktop) (PREEMPT)
CONFIG_PREEMPT:
This option reduces the latency of the kernel by making
all kernel code (that is not executing in a critical section)
preemptible. This allows reaction to interactive events by
permitting a low priority process to be preempted involuntarily
even if it is in kernel mode executing a system call and would
otherwise not be about to reach a natural preemption point.
This allows applications to run more 'smoothly' even when the
system is under load, at the cost of slightly lower throughput
and a slight runtime overhead to kernel code.
Select this if you are building a kernel for a desktop or
embedded system with latency requirements in the milliseconds
range.
Nr2
Timer frequency
Allows the configuration of the timer frequency. It is customary
to have the timer interrupt run at 1000 Hz but 100 Hz may be more
beneficial for servers and NUMA systems that do not need to have
a fast response for user interaction and that may experience bus
contention and cacheline bounces as a result of timer interrupts.
Note that the timer interrupt occurs on each processor in an SMP
environment leading to NR_CPUS * HZ number of timer interrupts
per second.
Prompt: Timer frequency
Location:
-> Processor type and features
Defined at kernel/Kconfig.hz:5
Selected by: m
1000 HZ (HZ_1000)
CONFIG_HZ_1000:
1000 Hz is the preferred choice for desktop systems and other
systems requiring fast interactive responses to events.
Symbol: HZ_1000 [=y]
Type : boolean
Prompt: 1000 HZ
Location:
-> Processor type and features
-> Timer frequency (<choice> [=y])
Defined at kernel/Kconfig.hz:42
Depends on: <choice>
Show Posts
