-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cn/gpu (cryptonight-gpu) algorithm support #928
Labels
Comments
Sample configuration to test new algorithm: {
"algo": "cryptonight",
...
"pools": [
{
"url": "tnpool.ryo-currency.com:3333",
"user": "RYoTr42cFt7f6V1EFpAESwMTat74xGiTKEt37PSmGAznX7SMkEz5iLNFMoLbwJCqhrAfAb5Jd3HKqUK3i6SoBaZQKHZrFWmz3jM",
"pass": "x",
"rig-id": null,
"nicehash": false,
"keepalive": false,
"variant": "gpu",
"tls": false,
"tls-fingerprint": null
}
],
...
} |
Has there been any benchmarking done? I ran some quick tests, but haven't tried messing with configs/gpu settings much yet. Hashrate for RX470/570/480/580 was between 500-600 h/s with "standard" cn/2 config settings:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In version 2.11 added support for new algorithm
cryptonight/gpu
, short aliascn/gpu
(original namecryptonight-gpu
), for upcoming Ryo currency fork on February 14.This algorithm very different, it heavy use floating point operations to hurt FPGAs and general purpose CPUs, hashrate balanced between AMD and NVIDIA GPUs, memory requirements decreased, core and power usage increased.
Only 3 things remaining from original cryptonight:
Notes
cn/*
variants, but generally it not so good idea, because optimal settings forcn/gpu
is different.Release
The text was updated successfully, but these errors were encountered: