Dogecoin ascii art catalogue
Global device settings autoconfigure - Enables automatic configuration for the selected device. Started by iBits Replies: Global settings autodetect - Sets which classes of devices should be automatically detected. This allows you miner control the kernel execution time to miner hashrate or reduce interface lag. With the default kernels Phoenix 2 support 3 classes of device: It's slightly faster than phoenix poclbm, but slower than the modified poclbm with the H.
Default is the maximum supported bitcoin the device. June 12, bitcoin, Phoenix by SMF 1. This allows you to control the kernel execution time to improve hashrate or reduce interface lag. This improves hashrate at lower aggression levels without introducing any additional interface lag. This can improve hashrate on supported devices.
Tweaking this setting may improve performance. May 10, , It appears that you have not registered with Bitcoin Forum. Online Bitcoin Miner Started by dodoking. August 04, , Bitty Miner Started by crrdlx. October 14, , September 22, , Which is fastest and efficient miner?? November 17, , June 12, , It loads kernels dynamically - If someone releases a more efficient kernel for our miner, it's as simple as dropping in the new kernel and using it.
It supports automatic failover by specifying a backup server with -b - Example usage To connect to a pool such as Slush's using our miner and Phateus's phatk2 kernel, you would use a command line such as: Accepted and rejected share counts should be pretty self-explanatory.
The protocol type indicates the type of connection: RPC servers with long poll have a different notification. This shouldn't need to be changed for most GPU miners. You might want to lower this for longer kernel execution times. The correct protocol is selected based on the prefix RPC for http: It supports automatic failover by specifying a backup server with -b - Example usage To connect to a pool such as Slush's using our miner and Phateus's phatk2 kernel, you would use a command line such as: Accepted and rejected share counts should be pretty self-explanatory.
The protocol type indicates the type of connection: RPC servers with long poll have a different notification. This shouldn't need to be changed for most GPU miners. You might want to lower this for longer kernel execution times. The correct protocol is selected based on the prefix RPC for http: The backup server will be used if the primary server is down.
Works exactly like -u. All other arguments MUST come before specifying a kernel. Any arguments after -k are sent to the kernel. This isn't needed if you only have a single platform. This isn't needed if you only have a single device. This may improve hashrate if enabled, but it can be slower on some hardware. Tweaking this setting may improve performance similar to poclbm's -w flag. Default is the maximum supported by the device. This significantly improves hashrate.
However, it no longer results in stale shares. The phatk and phatk2 kernels don't work well Nvidia GPUs. Use poclbm kernel instead. For optimal performance use either SDK 2. These settings are intended only as a starting point, and may not be optimal for your system configuration.
Phoenix Miner developer Donations appreciated at: Mixing reinvented for your privacy Chip Mixer.