OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 798.

phase

newbie

Activity: 49

Merit: 0

Quote from: sharky112065 on August 21, 2011, 06:12:10 AM

It is really stupid regardless of whether you are on Linux or Windows to have to run multiple instances. Especially since Cgminer is already set up to use all GPU's with one worker and display stats on one screen. Why would you want to have multiple screens that you have to toggle just to get stats.

Well, on Windows and even on Linux, there is this neat trick that allows you to resize windows and fit them all on one screen, it's quite amazing frankly.. Wink

Quote from: sharky112065 on August 21, 2011, 06:12:10 AM

Windows CPU usage can be reduced using affinity so I'm not worried about that.

Then why worry about running 3 extra processes?

Quote from: sharky112065 on August 21, 2011, 06:12:10 AM

Given how Cgminer seems to work now, I would think (but I do not know) it would be easy to add another cmd line option to use different login names per GPU.

Load balancing / failover, pool connections, work and login data are currently shared among one process and all GPU's enabled for that process. The command line arguments would have to be extended and the logic further complicated to detect if you are loading data for one GPU and/or multiple GPU's, for those that want to pass all this info via command-line instead of configuration files, etc... If con were to add what you ask, he would have to split all of this logic off on a per-GPU level, adding extra complexity to the miner, for something that is basically a moot point. This is probably just the tip of the iceberg. If you really want this, I'd suggest starting out with a donation. Wink

I can think of a good reason to run one instance per GPU. If a GPU dies, you can't always restart it from within cgminer. With one GPU per instance, you can have a script checking stats (cgminer output piped to log file, or core temperature with single-core cards) for each GPU and automatically kill/restart instances of cgminer with a dead GPU.

cirz8

newbie

Activity: 42

Merit: 0

Quote from: sharky112065 on August 21, 2011, 05:58:10 AM

Quote from: cirz8 on August 21, 2011, 05:44:02 AM

If one has problems with Miner/GPU/Worker going down from time to time, one should have the whole process of restoring them automated.
Much easier to do in linux, but can be done in windows too, just easier in linux.

At some point one will have need to manually perform maintenance, even when running Linux. Having separate workers for Computer/GPU, makes targeting that Computer/CPU that much easier.

I don't have to touch my rigs even if there is a hard lock, unless I want to.
Sure, if some hardware fails physically there is not much any automated software can do about it unless you have a robot available.
But such a failure would be displayed in the monitoring logs/graphs as that rig would stop responding or report very odd values.

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: phase on August 21, 2011, 05:59:42 AM

As said, you can achieve this by simply running separate instances of the miner for every GPU.. You have 4 single-GPU cards, so you assign one instance of cgminer to each card, presto. Yes, those 3 extra processes are totally going to drive down your efficiency and clutter your system... Why don't you start by switching over to Linux, if you want to increase efficiency, since cgminer is known to have high CPU usage on Windows due to porting. Set up some scripts and you're good to go.

Oh my god.

It is really stupid regardless of whether you are on Linux or Windows to have to run multiple instances. Especially since Cgminer is already set up to use all GPU's with one worker and display stats on one screen. Why would you want to have multiple screens that you have to toggle just to get stats.

Windows CPU usage can be reduced using affinity so I'm not worried about that.

Switching to Linux at this point would take quite a bit of time for all of my computers and still does not solve the problem. A lot of people like to run on Windows (Bloated that it is) rather than Linux because it is far easier.

Given how Cgminer seems to work now, I would think (but I do not know) it would be easy to add another cmd line option to use different login names per GPU.

phase

newbie

Activity: 49

Merit: 0

As said, you can achieve this by simply running separate instances of the miner for every GPU.. You have 4 single-GPU cards, so you assign one instance of cgminer to each card, presto. Yes, those 3 extra processes are totally going to drive down your efficiency and clutter your system... Why don't you start by switching over to Linux, if you want to increase efficiency, since cgminer is known to have high CPU usage on Windows due to porting. Set up some scripts and you're good to go.

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: cirz8 on August 21, 2011, 05:44:02 AM

If one has problems with Miner/GPU/Worker going down from time to time, one should have the whole process of restoring them automated.
Much easier to do in linux, but can be done in windows too, just easier in linux.

At some point one will have need to manually perform maintenance, even when running Linux. Having separate workers for Computer/GPU, makes targeting that Computer/CPU that much easier.

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: -ck on August 21, 2011, 05:07:19 AM

Everyone thinks the feature they want is the killer feature.

* ckolivas gets his eyesight checked

I'm just surprised you did not think it was a necessary feature given that pool's allow users to set up multiple workers per GPU and display stats per worker.

I spent quite a bit of time playing with command line options trying to get it to work just assuming that it was possible given, that running it with just one pool automatically sets up all GPU's to that worker/login and display's on one screen.

In fact people in BTC Guild IRC channel told me it could not be done and I just could not believe it and stubbornly went ahead and fiddled with options.

But they were correct. Sad

phase

newbie

Activity: 49

Merit: 0

Quote from: -ck on August 21, 2011, 05:07:19 AM

Everyone thinks the feature they want is the killer feature.

* ckolivas gets his eyesight checked

Con, please add SETI support. Without it, cgminer is pretty useless to me, unless I put in some effort to run a separate program.. But, you know, bleh! By the way, if you add this feature, there won't be any reason left for anyone to use another miner, ever again! Cool

cirz8

newbie

Activity: 42

Merit: 0

If one has problems with Miner/GPU/Worker going down from time to time, one should have the whole process of restoring them automated.
Much easier to do in linux, but can be done in windows too, just easier in linux.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Everyone thinks the feature they want is the killer feature.

* ckolivas gets his eyesight checked

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: d3m0n1q_733rz on August 21, 2011, 01:54:39 AM

Quote from: -ck on August 21, 2011, 01:28:31 AM

Quote from: sharky112065 on August 20, 2011, 09:07:32 AM

I'm trying to set up one of my computers with Cgminer and am having a problem.

I have 4 6970's in the computer and I want to connect them to Deepbit as primary and BTC Guild as backup.

I want to only have one instance of Cgminer running and be able to use one pool worker per GPU (Not all 4 GPU's using one login and password). This is needed because I check the status on my phone of my miners to see if any of them have stopped. If they are all lumped into one login, I have no way of knowing which GPU is having an issue.

So for Deepbit and BTC Guild I have 4 workers set up (One for each GPU).

Using Windows 7. No Screen command so I only want one instance of Cgminer running.

I have tried the "-d" option for all GPU's but that doesn't seem to work for me.

Any way to make this happen?

Not currently, unless you run multiple instances of cgminer, one for each pool, bound to just one GPU.

cgminer -d 0 -o pool1...
cgminer -d 1 -o pool2...
cgminer -d 2 -o pool3...

I have no intention of adding the feature of binding one pool to one gpu as it's a really inefficient way of managing resources in my opinion, and you can get the same effect by running multiple instances of cgminer anyway.

I don't believe he was saying one pool per GPU, he was saying one username per GPU for a single pool. As for right now, in order to setup one username per GPU, it will be easier to toss together a batch file to run than to just type them all into multiple cmd prompts. Utilize the start command in your batch file so that it won't wait for the program to end before continuing on to run the next instance. It's a nice idea using a different username for each GPU to view its efficiency/shares; and it would be very difficult to output the live status of cgminer directly for viewing on a mobile device without logging into your computer to do so.
It should be a simple add for the command input portion by using an "If userpass defined for device, set userpass for device; else use previously defined", but submitting the results for and having each thread with a separate --userpass would be tricky to say the least. Not impossible, but tricky.
It's a nice feature request though. Roll Eyes

If I were running on Linux it would not be an issue as I could just use the screen command.

On windows, running 4 separate windows (one per GPU) looks like a cluster F**K (especially at 1024/768). I have an 8 port KVM that I switch between computers.

Cgminer already will use my 4 GPU's showing on one screen in windows, I just cannot have each GPU using a separate login name on the pool.

I monitor my workers remotely using http://www.btc-poolwatch.com/ on my phone and by using separate workers for each GPU, I can see when a Miner/GPU/Worker goes down. Ex. BC1-0, BC1-1, BC1-2, BC1-3, BC2-0, BC2-1 ... Using those workers, I can immediately tell which computer and which GPU is having issues.

I am able to do this in Guiminer, just wanted to be able to do it in Cgminer. Without it it is kinda useless for me unless I were to take the down time and convert all my computers over to Linux.

Also the author said he thought that would be inefficient, but I disagree. I think running 4 separate instances is inefficient and awkward.

I think it is a bit short sighted to not include this functionality (Pools allow multiple workers for a reason, be it multiple computers, multiple GPU's or for monitoring).

If he were to include the multi worker functionality I think not many people would ever have a reason to be using Guiminer.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Long term output shows how evenly things really are:

Code:

cgminer version 1.5.6 - Started: [2011-08-18 14:12:33]
--------------------------------------------------------------------------------
 [(5s):1722.8  (avg):1707.8 Mh/s] [Q:62194  A:108778  R:1067  HW:0  E:175%  U:23.37/m]
 TQ: 8  ST: 14  LS: 0  SS: 68  DW: 9763  NB: 455  LW: 87419  LO: 0  RF: 41  I: 8
 Connected to multiple pools with LP
 Block: 0000052fe78561692640d8cdd37355fe...  Started: [19:23:50]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0: [428.7 / 427.0 Mh/s] [Q:14807  A:27015  R:278  HW:0  E:182%  U:5.80/m]
 GPU 1: [422.9 / 426.9 Mh/s] [Q:15194  A:27264  R:293  HW:0  E:179%  U:5.86/m]
 GPU 2: [426.9 / 427.0 Mh/s] [Q:14687  A:27075  R:238  HW:0  E:184%  U:5.82/m]
 GPU 3: [429.0 / 426.9 Mh/s] [Q:14804  A:27425  R:258  HW:0  E:185%  U:5.89/m]
--------------------------------------------------------------------------------

@Okama: I wouldn't pay much attention to the rates till much longer has passed. If you get different rates after many hours, check stability of different cards (see mine for how stable the rates can be long term with identical cards).

Okama

newbie

Activity: 23

Merit: 0

Quote

GPU 0: [361.3 / 360.7 Mh/s] [Q:13 A:14 R:0 HW:0 E:108% U:4.73/m]
GPU 1: [373.0 / 369.6 Mh/s] [Q:5 A:12 R:0 HW:0 E:240% U:4.06/m]
GPU 2: [327.7 / 326.5 Mh/s] [Q:1 A:10 R:0 HW:0 E:1000% U:3.38/m]
GPU 3: [352.0 / 349.4 Mh/s] [Q:5 A:10 R:0 HW:0 E:200% U:3.38/m]

GPU 0&3 (5850) has the same clocks 875/300, but the speed is a little different. The params which I use is

Quote

-I 8 -k phatk -w 256 -v 2

With phoenix 1.6.2,

Quote

-k phatk2 WORKSIZE=256 AGGRESSION=12 BFI_INT FASTLOOP=false VECTORS

their performance are nearly the same (~365MHash/s)

My 5870s on the other system also has the same issue.

My Linux box is Ubuntu 11.04 with AMDAPP v2.5, fglrx 8.861.

d3m0n1q_733rz

sr. member

Activity: 378

Merit: 250

Quote from: -ck on August 21, 2011, 01:28:31 AM

Quote from: sharky112065 on August 20, 2011, 09:07:32 AM

I'm trying to set up one of my computers with Cgminer and am having a problem.

I have 4 6970's in the computer and I want to connect them to Deepbit as primary and BTC Guild as backup.

I want to only have one instance of Cgminer running and be able to use one pool worker per GPU (Not all 4 GPU's using one login and password). This is needed because I check the status on my phone of my miners to see if any of them have stopped. If they are all lumped into one login, I have no way of knowing which GPU is having an issue.

So for Deepbit and BTC Guild I have 4 workers set up (One for each GPU).

Using Windows 7. No Screen command so I only want one instance of Cgminer running.

I have tried the "-d" option for all GPU's but that doesn't seem to work for me.

Any way to make this happen?

Not currently, unless you run multiple instances of cgminer, one for each pool, bound to just one GPU.

cgminer -d 0 -o pool1...
cgminer -d 1 -o pool2...
cgminer -d 2 -o pool3...

I have no intention of adding the feature of binding one pool to one gpu as it's a really inefficient way of managing resources in my opinion, and you can get the same effect by running multiple instances of cgminer anyway.

I don't believe he was saying one pool per GPU, he was saying one username per GPU for a single pool. As for right now, in order to setup one username per GPU, it will be easier to toss together a batch file to run than to just type them all into multiple cmd prompts. Utilize the start command in your batch file so that it won't wait for the program to end before continuing on to run the next instance. It's a nice idea using a different username for each GPU to view its efficiency/shares; and it would be very difficult to output the live status of cgminer directly for viewing on a mobile device without logging into your computer to do so.
It should be a simple add for the command input portion by using an "If userpass defined for device, set userpass for device; else use previously defined", but submitting the results for and having each thread with a separate --userpass would be tricky to say the least. Not impossible, but tricky.
It's a nice feature request though. Roll Eyes

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: sharky112065 on August 20, 2011, 09:07:32 AM

I'm trying to set up one of my computers with Cgminer and am having a problem.

I have 4 6970's in the computer and I want to connect them to Deepbit as primary and BTC Guild as backup.

I want to only have one instance of Cgminer running and be able to use one pool worker per GPU (Not all 4 GPU's using one login and password). This is needed because I check the status on my phone of my miners to see if any of them have stopped. If they are all lumped into one login, I have no way of knowing which GPU is having an issue.

So for Deepbit and BTC Guild I have 4 workers set up (One for each GPU).

Using Windows 7. No Screen command so I only want one instance of Cgminer running.

I have tried the "-d" option for all GPU's but that doesn't seem to work for me.

Any way to make this happen?

Not currently, unless you run multiple instances of cgminer, one for each pool, bound to just one GPU.

cgminer -d 0 -o pool1...
cgminer -d 1 -o pool2...
cgminer -d 2 -o pool3...

I have no intention of adding the feature of binding one pool to one gpu as it's a really inefficient way of managing resources in my opinion, and you can get the same effect by running multiple instances of cgminer anyway.

dishwara

legendary

Activity: 1855

Merit: 1016

In windows version of cgminer, there is nothing to install. Just extract & use.
Symantec SEES wrong code in cgminer.exe & deletes it.
You want Symantec to just delete the wrong code only?
Then it should have the PURE cgminer.exe.
So that it compares both & removes the just botcode.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: dishwara on August 20, 2011, 10:10:44 AM

What Symantec doing may be dumb, stupid, moronic to you, but it alerts me that my system may get affected & it stops my system from affecting.
Antivirus, Anti-malware, Firewall....are used to PROTECT system.
I am happy Symantec doing that.
& i am not a runner like some to run to Linux coz Windows gets virus.
Most of the virus created for Windows by anti virus companies to do business. If there is no virus then there is no need for antivirus, then antivirus companies have to close.
Since Linux not used by many & it still lacks in number of software available to Linux comparing to Windows vast number of softwares for a particular thing & many Linux programmers also writing viruses to show the hate of the monopoly of Windows, Linux is safe now.
But if it comes in mainstream like Windows it too will have virus & you will run to some other OS.

How did pointing out a stupid flaw (caused by programming stupidity) with Symantec detecting cgminer.exe as a trojan turn into me being a "Windows runner" ?
I even pointed out 3 Windows AV programs that do not currently delete a completely benign program from your system.
So will you be happy and think it is smart when Symantec starts deleting, in the near future, whatever Bitcoin Miner program you use?

Again: (for the 3rd time - since you still don't seem to understand the blatantly obvious)
Symantec does not detect the trojan program that effects your PC.
The program that effects your PC is the bot code that installs cgminer.exe and that should be what it detects and removes.
Instead Symantec says it detects cgminer.exe as a trojan (which it isn't) and then removes it!

I've used linux since 1997.
My desktop and servers at home are all linux (except my kids PCs) and have been linux for most of those 14 years.
I am required by the Australian Government to run Windows to be able use their BAS software for my work and do my Tax so I run them (once every 3 months) in a VirtualBox with a valid paid for Windows XP license.
I base my OS decision on my extensive knowledge of software, programming and OS internals and design.

shaps

newbie

Activity: 15

Merit: 0

Quote

Shaps, that's not the best algo. The cryptoasm_x64 is the best algo. You're using either the C miner or 4Way.

d3m0n1q_733rz, when I check --help, the only options for algo are c, 4way, via, cryptopp, cryptopp_asm32 (and auto). If you try to specify "cryptoasm_x64" you get an "Unknown algorithm" error. Am I missing something?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: gnar1ta$ on August 20, 2011, 03:34:57 PM

This is what I'm seeing a lot:

Code:

[2011-08-20 20:27:31] GPU 0  Q:2849  A:3952  R:181  HW:0  E:139%  U:3.29/m

[2011-08-20 20:27:38] HTTP request failed: Operation timed out after 60001 millisecon
ds with 0 bytes received
[2011-08-20 20:27:38] submit_upstream_work json_rpc_call failed
[2011-08-20 20:27:38] Pool 0 communication failure, caching submissions

[2011-08-20 20:27:38] Stale share detected, discarding
[2011-08-20 20:27:42] [(5s):719.9  (avg):684.3 Mh/s] [Q:5973  A:7892  R:356  HW:0  E:
132%  U:6.57/m]
[2011-08-20 20:27:47] X-Roll-Ntime found
[2011-08-20 20:27:47] Pool 0 communication resumed, submitting work

[2011-08-20 20:27:47] Accepted e1b2aa64 GPU 1 thread 1 pool 0
[2011-08-20 20:27:47] GPU 1  Q:2928  A:3941  R:175  HW:0  E:135%  U:3.28/m

[2011-08-20 20:27:48] [(5s):710.1  (avg):684.3 Mh/s] [Q:5973  A:7893  R:356  HW:0  E:
132%  U:6.57/m]

[2011-08-20 20:27:56] HTTP request failed: Operation timed out after 60001 millisecon
ds with 0 bytes received
[2011-08-20 20:27:56] Failed json_rpc_call in get_upstream_work
[2011-08-20 20:27:56] json_rpc_call failed on get work, retry after 5 seconds

I think it's from a network issue where my latency will jump from 40 to 700, and since only one ISP is available and they don't believe lightning hitting their equipment is an issue, is there any settings I can adjust to try to compensate and reduce stales?

You could try decreasing the stale rate overall by running less threads per GPU with '-g 1'. While it will decrease your mhash slightly, it might be worth the compromise since the share submissions will start happening earlier (since each thread will find shares in less time).

gnar1ta$

donator

Activity: 798

Merit: 500

This is what I'm seeing a lot:

Code:

[2011-08-20 20:27:31] GPU 0  Q:2849  A:3952  R:181  HW:0  E:139%  U:3.29/m

[2011-08-20 20:27:38] HTTP request failed: Operation timed out after 60001 millisecon
ds with 0 bytes received
[2011-08-20 20:27:38] submit_upstream_work json_rpc_call failed
[2011-08-20 20:27:38] Pool 0 communication failure, caching submissions

[2011-08-20 20:27:38] Stale share detected, discarding
[2011-08-20 20:27:42] [(5s):719.9  (avg):684.3 Mh/s] [Q:5973  A:7892  R:356  HW:0  E:
132%  U:6.57/m]
[2011-08-20 20:27:47] X-Roll-Ntime found
[2011-08-20 20:27:47] Pool 0 communication resumed, submitting work

[2011-08-20 20:27:47] Accepted e1b2aa64 GPU 1 thread 1 pool 0
[2011-08-20 20:27:47] GPU 1  Q:2928  A:3941  R:175  HW:0  E:135%  U:3.28/m

[2011-08-20 20:27:48] [(5s):710.1  (avg):684.3 Mh/s] [Q:5973  A:7893  R:356  HW:0  E:
132%  U:6.57/m]

[2011-08-20 20:27:56] HTTP request failed: Operation timed out after 60001 millisecon
ds with 0 bytes received
[2011-08-20 20:27:56] Failed json_rpc_call in get_upstream_work
[2011-08-20 20:27:56] json_rpc_call failed on get work, retry after 5 seconds

I think it's from a network issue where my latency will jump from 40 to 700, and since only one ISP is available and they don't believe lightning hitting their equipment is an issue, is there any settings I can adjust to try to compensate and reduce stales?

twmz

hero member

Activity: 737

Merit: 500

I decided to give cgminer another try (latest version) on my linux rigs. Again, within 24 hours, on my 2x5970, 1x6850 rig, 3 of the 5 GPUs were marked DEAD. And this was with the GPUs underclocked from factory defaults. Note, poclbm and phoenix (including with the latest phatk kernel) never stop working like this even after 7+ days of non-stop mining on the same rig with overclocked GPUs. I don't know if Python's OpenCL connectivity is just more reliable than what cgminer is doing, but I can say that something is pretty conclusively wrong with cgminer relative to other other miners this rig.

I like the idea of cgminer, but saddly will return to running 10 instances of poclbm because that is at least rock solid stable even if it is annoying to manage.

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 798. (Read 5805728 times)