filmes porno buceta gostosa phim sex www xxnxx com xxxvideos porno Xvideos Com

Search Results

ccminer-1-7-4-tpruvot-vanillacoin

We have compiled ccMiner 1.7.4 tpruvot’s fork Windows binary in a version with the optimal settings for mining Vanillacoin (VNL) on more recent Nvidia-based GPUs as suggested by Alexis Provos and with his performance optimizations as implemented by tpruvot in the latest code. This Windows binary is a 32-bit one compiled with CUDa 6.5 and only with Compute 3.5 support as apparently this provides the optimal performance at least on Maxwell-based Nvidia GPUs (Faster than using Compute 5.2 on them). Below you can also see a comparison that we did with Nvidia GeForce GTX 970 from Gigabyte (WF3OC) and a reference design Gigabyte GTX 980 Ti to see the difference in performance with the regular version when using CUDA 7.5 and Compute 5.2 and with the optimized CUDA 6.5 and Compute 3.5 version available for download below. Do note that although this binary will work with other algorithms as well as the Blake 256 8-rounds used by VanillaCoin it may not provide the optimal performance for other algorithms as it is targeted to provide the best VNL mining hashrate.

GeForce GTX 970 – CUDA 7.5 Compute 5.2
Default – 2490 MHS @ 164 W
Intensity 25 – 2535 MHS
Intensity 26 – 2637 MHS
Intensity 27 – 2692 MHS
Intensity 28 – 2718 MHS
Intensity 29 – 2722 MHS
Intensity 30 – 2729 MHS
Intensity 31 – 2732 MHS

GTX 980 Ti – CUDA 7.5 Compute 5.2
Default – 3390 MHS @ 211 W
Intensity 25 – 3797 MHS
Intensity 26 – 3884 MHS
Intensity 27 – 3986 MHS
Intensity 28 – 4009 MHS
Intensity 29 – 4043 MHS
Intensity 30 – 4075 MHS
Intensity 31 – 4132 MHS

GeForce GTX 970 – CUDA 6.5 Compute 3.5
Intensity 31 – 2942 MHS @ 177 W

GeForce980 – CUDA 6.5 Compute 3.5
Intensity 31 – 4418 MHS @ 238 W

Do note that increasing the intensity over the default setting (no manual -i intensity option used) even on a regular release will provide some increase in performance as you can see in our comparison going up to the maximum supported intensity of 31. Have in mind that increasing intensity also makes the system a bit less responsive the higher you go and at 30/31 it will be lagging more, but the extra performance gain you will get with the optimal binary and higher Intensity setting is significant, so for a dedicated mining rig for VanillaCoin you should definitely go for it.

Update: This particular performance optimization is for VanillaCoin’s Blake256 8-rounds implementation, the CUDA 6.5 and Compute 3.5 compilation of the particular CUDA code for that algorithm give better performance than Compute 5.0 or 5.2. The CUDA code is different for other Blake 256 algorithms, including the one for Decred’s Blake-256 14-rounds implementation, so do not expect performance increase in others. In fact specifically for Decred, a 64-bit compilation with CUDA 7.5 and for Compute 5.x does seem to provide best performance with the publicly available ccMiner 1.7.4 fork from tpruvot.

To download the ccMiner version 1.7.4 by tpruvot for VanillaCoin mining for Windows OS…

nvidia-smi-p2-power-state

There is a little trick that can help you get some extra hashrate out of your Nvidia GPU when mining Ethereum or another more memory dependent algorithm, though it will most likely not affect many of the other crypto algorithms. By default when running Compute applications on your GPU it does not go to the highest Power State of the card, meaning that you might not be able to squeeze the maximum performance out of the video card and that is without overclocking anything. Thanks to the Nvidia System Management Interface (nvidia-smi) command line utility you are able to force the GPU to work in P0 state (the highest power state) instead of staying at maximum P2 when running a Compute applications such as a crypto miner software. Do note that this specific lower maximum power state is only for Compute applications, so it is not needed, not it should affect gaming performance where the GPU shuld go up to P0 power state if the conditions allow it.

The nvidia-smi utility is part of the video drivers and you can find it installed in the folder “C:\Program Files\NVIDIA Corporation\NVSMI\” on Windows, so you need to run the command line (cmd) and navigate to that folder in order to be able to issue commands. What you should start with is running the following command to check the current P-state of your GPU(s):

nvidia-smi -q -d PERFORMANCE

Do note that the P-state changes dynamically, so you need to be running Ethminer or another application when you issue the above command to see the power state active under load, otherwise you might see a lower power state being active if the GPU is idle.

nvidia-smi-p0-operating-frequencies

After you verify the maximum power state that your Nvidia GPUs use when executing Compute applications such as ones that rely on OpenCL or CUDA you need to check what are the maximum frequencies of the video card that are available for the maximum performance in the P0 power state. You can do so with the following command (make sure you are still in the NVSMI folder):

nvidia-smi -q -d SUPPORTED_CLOCKS | more

The above will list all of the supported frequencies in the different power states that your video card can use, but there is no need to check the complete list. All we need to note are the frequencies at the top of the list for the Memory and the Graphics, in this example we are using GTX 970 video card from Gigabyte and the values we need are 3505 MHz for the VRAM and 1455 MHz for the GPU. We’ll need these frequencies for the next step.

nvidia-smi-p0-power-state-activated

What we are going to do next is to force the video card to use the maximum performance operating frequencies by going to the P0 power state. In order to do that we need to run the following command:

nvidia-smi -ac 3505,1455

Note that the above command will apply the settings to all GPUs that you have in your system, normally that should not be a problem for most mining rigs as they are usually with a number of cards that are the same model, but there are cases when this is not true. So you might need to check the individual settings fro different video cards and apply the correct parameters for each of them separately. To do so you just need to add the card ID in the command line, so that the particular option will be executed only for the specified video card. This is being done by adding the “-i ” parameter to the command line where can be a number starting from 0 for the first GPU and so on. In the example shown on the screenshot above we have two different GPUs in the system, so wee need to set their P0 power states with two separate commands identifying each of the card separately:

nvidia-smi -i 0 -ac 3505,1455
nvidia-smi -i 1 -ac 3505,1392

The question that undoubtedly comes now is how we have increased the performance for mining Ethereum by following the instructions above. Well it is pretty easy to check by running a benchmark with Ethminer, or just running the miner and noting the new increased frequencies that you should now have and compare them to the ones you previously had. On the Nvidia Gigabyte GTX 970 WF3OC video card used in the guide we are normally getting about 17.31 MHS in terms of hashrate mining Ethereum when the GPU is maxing out at the P2 power state, when we force it to go to the P0 power state the hashrate increases to about 19.98 MHS. So this is a nice improvement in terms of performance that comes at a cost of just about 10W higher power usage from the video card. Do note however that while this will work with Ethereum for increasing performance due to the heavy usage of video memory in the mining process, doing it may not bring performance improvement in many other commonly used mining algorithms.

ccminer-spmod-cuda-65-vs-75

The ccMiner SPMOD fork for Nvidia Maxwell GPUs (source) has recently been migrated to use the newer CUDA 7.5 from the older CUDA 6.5. The latest version with CUDA 6.5 support was version ccMiner 1.5.74 and the latest version is ccMiner 1.5.78 that already uses CUDA 7.5. The first release with CUDA 7.5 had not so good performance and was slower in some algorithms in terms of performance as compared to the latest CUDA 6.5 release, but the latest code has been optimized to offer similar or even better hashrate in most supported algorithms. We took an Nvidia GeForce GTX 970 (Gigabyte GV-N970WF3OC-4GD) running at stock frequencies for a spin with some of the currently popular algorithms to compare the performance of the latest CUDA 6.5 to the latest CUDA 7.5 release of ccMiner spmod. The results in the table clearly show that aside from NeoScrypt the latest CUDA 7.5 release offers very similar or even slightly better hashrate compared to the latest CUDA 6.5 version. The hashrate of X13, X15 and Qubit is still slightly slower, but not much. So unless you are mining NeoScrypt you should have no reasons not to upgrade to the newer CUDA 7.5 releases and soon we are probably going to see even better performance thanks to further optimizations of the code. Do note however that some other Maxwell GPUs might have some more variance in terms of performance difference between the two compared versions.


top