Update regexes for gminer to support multiple GPUs #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mm.js currently only grabs the hashrate from the first GPU when benchmarking gminer. This updates the current regexes to return the total hashrate value if more than one GPU exists.
Example 1 - GMiner 87F5 output for single GPU:
Example 2 - GMiner output for multi-GPU:
Previously mm.js would return the hashrate of GPU 0 for both examples. i.e. 27.09 for example 1 and 51.74 for example 2. With the updated regexes it now returns the total hashrate in both examples... 27.09 for example 1 and 272.17 for example 2.