Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 153. (Read 794394 times)

ScryptJaneNf16.

For CPU, what's the current most profitable algo to use on nicehash on E3-1240v3?

Totally understandable, thanks for the quick response.
Autostart is the most important one to prevent botnets from using it in my opinion, though that's a nice feature to have for legit users too.  Catch 22 for sure.
Wonder if there would be a way to require user interaction once, to generate a random start up key or something, that would only work for that hardware set, similar to how games have a unique GUID.
This way if they tried to deploy it via a botnet, every infected machine would need to do a certain task to create the autostart UserID.  Or something that could be done via the nicehash site etc.  Just a random idea I'm not much of a coder lol.

Either way amazing idea and work!

Once we have a good idea how to prevent botminers, we can make an autostart, autobenchmark command line options, that could simply what you would like to achieve. But that is not something to arrive so soon, we have other priorities, like adding AMD support, so you better just manually benchmark them - it just few clicks

3. Hardware ranges from X3470, E3 v1, v2 and v3 of various models 1230-1270.  I can just manually benchmark them for now, was just a feature idea I had.

4. Will debug and check more on this.

3. If you have same hardware on all machines, you can run benchmark on one, then just copy config.json to all other machines.

4. You may try to debug this by manually launching benchmark. If you define config to launch with console, you will see startup parameters. Use the same parameters and see what will happen. It is possible that cpuminer instance crashes for some reason - in such case Terminated would be written, but after benchmark is complete, cpu averaging kicks and may hide the "Terminated" result with speed 0.

1 and 3. This would be a useful feature as I run this on my home PC and several dedicated servers I bought to originally mine MemoryCoin(that didn't turn out well).  Some of them I run multiple programs on and manually checking benchmark on each could be a hassle. Currently I just run Monero on them and manually tuning each one took a few minutes to find the optimal value.  Having profit switching would be great(also any plans on adding CryptoNight algorithm?).  Perhaps a better idea would only on the first run, or any time a new version if available of NiceHashMiner?

4. I used this on several E3-1240v3 and got 0.00 for all 3 values running Windows Server 2008 R2.
I manually ran them and got 580KH, .05KH and .03KH on 4 cores so something with the benchmark tool seems off.  On the X3470, only lyra2re showed a value which was accurate, while on the E3 v3 it showed 0.00 for all 3 CPU values.  I tried the fast, normal, and lengthy benchmark and got the same result.

6. Did not notice it already started in idle priority, this is what I was wanting to do, though having the option of running it as below normal might be nice for sets of hardware I run nothing else on?  Doesn't really seem to make a difference in hash rate either way.

Very nice tool. I have been waiting something like that since Miner Control looks dead. Even Kbomba seems to gave up. There is a lot of job ahead of You. Here are some thing I miss from MinerControl: reload, autostart, integrated console, and more detail tabs (hashrate, price, earn,... I know that newer versions will have some of this things included.

BR, and keep the good work...

1. A % or LessThreads gives you the same end effect - controlling number of threads to execute. Giving more parameters regarding this matter would only make config more bloated and confusing. We will keep single value. Everyone can easily calculate what 40% means for their PC. And considering fact that you do not change hardware every day, you need to perform this calculation manually only once.

2. We will add autostart later once we have final product and when some additional system checks are performed. We do not want this tool to become something botnet users would use.

3. Benchmarking every X hours would mean that current active mining is stopped. Probably not something the majority want. The hardware does not change while PC is running and we see no benefit of doing benchmark re-evaluation over time. Neither did you explain why re-evaluation over time would be needed at all.

4. We will probably make more decimal places being displayed. Your CPU is probably very slow for Axiom and ScryptJane, because it doesn't have AVX (and both mentioned algorithms are AVX optimized).

5. Command line options are not supported yet for the same reason as - read point 2.

6. CPU mining priority is automatically set to lowest by cpuminer. The reasons why someone would want to mine with higher priority are unknown to us, but on another side, botnet users would gladly exploit this functionality.

Like i thought. Roskomnadzor made it harder. Had to use proxy sites.

Really like the new NiceHashMiner.
Couple of feature questions/suggestions.
Could you add a % value as well as "less cores" ?
Autostart option in the config file or command line argument?

Such as, only use 40% of cores, rounded up or down or try to use 40% of total CPU, whichever is easiest to program.
A way to have the benchmark run every X hours to re-evaluate itself?
Currently on an X3470 I'm getting 0.00KH for both Axiom and scryptjanenf16, not sure if a longer decimal value needs to be used for those with a weaker CPU.
450KH with lyra2re
Command line arguments to override config.json values such as -lesscpu 4
A priority setting would also be useful.

What is the daily profit percentage by cloudmining in this site? An estimate as of now will do.

What kind of error do you get? Does it say that cloudflare is working?

We are using Cloudflare as proxy for all web and API requests. Is Cloudflare working for you?

You may want to check latest 1.1.0.1 now and report back how it goes.

Ok thanks for all your help & the miner

Hi guys! Ive found that web site in unavailable from some ISPs from Russia. Im gatting ERR_CONNECTION_CLOSED from different ISPs.

Does anybody have the same issues ?

The manual values would be more accurate. Sadly the ccminer benchmark gets only accurate when running for long time, like several minutes. It is not as accurate as cpu benchmarking where we can get good exact results after few seconds already. Don't be afraid to use manually entered numbers (if you know how to).

Of course, our goal is to make good benchmarking part of the tool, because we know that not all users are capable of setting config files on their own.

We will take a deeper look into ccminer benchmarking issues and provide fix in following versions.

I have a 970 & a 750ti so both are nvidia5.x. Yeah i can plug in the values in config file but it wont be as accurate as the miner itself so i thought i will just report the bug here.

There are plans to somehow get rid of these issues. We rely on existing benchmark solutions by sp and tpruvot. Would you mind telling us what kind of video cards you have and whether benchmark was stuck for NVIDIA5.x or NVIDIA3.x.

Temporary solution for your problem is to manually adjust benchmarked values in config.json file.