ive put in a i5 quad core 2400s and i get a much more stable 380h/s all 4 cores at 71%
i tried two threads but hash rate went down to 135h/s on each thread and cpu was 100% on all cores.
The -I intensity doesn't seem to be the best thing in the world, defiantly far too cpu bound for a gpu miner. but its v1 prob so its expected.
I suggest you to try three instance of ./miner,look my reply above
Sorry I meant not 2 threads but I meant two instances. I logged into Linux as miner and ran the miner. (All cores at 70%.) Then fired up another ssh logged in as root and ran the miner. And the sum of the two hash rates was less than just 1. I don't know how yours can be so much better with similar systems?
I'm running on smos. And killed all the processes. Is the i5 2500s just not as powerful? It has 4 real cores
System: HiveOs
Ram : 4 gb(was not enough so i created another 4 gb of swap)
To start the miner i use this script: https://pastebin.com/gR2e1bp5 (i created a file called start.sh)
Every start.sh has my wallet and the worker number, example:
bm1qnsk9rl45s4kps6mm97393gdjr5hslf4hvu9ru2.001
bm1qnsk9rl45s4kps6mm97393gdjr5hslf4hvu9ru2.002
bm1qnsk9rl45s4kps6mm97393gdjr5hslf4hvu9ru2.003
I think i could do more hash if only i had a quad core.
Oc: +150 clock
Hmm weird why at one instance I'm at 4 cores at 70%. Do you remember your cpu usage with just one instance.
Would me running 1 instance as user miner. And an other as root cause a problem? Surely it just multitasks the same. No matter how the instances are run
I was getting 120% cpu with one process (200% limit because cpu is dual core), with three process i'm getting 70% - 70% - 60& (again, 200% limit), so i was planning to get a quad core (i3 or i5) to give each process the max requested (120% in my case).
EDIT: i tried with 6 core cpu and was using the same 100% of cores, so i think it's a combined cpu-gpu
Sorry to labour the point but I was at 70%-70%-70%-70% on one instance with 4 x1060 rock steady 380h/s
Adding an extra Instance yielded 100% across 4 cores and 135h/s on each core. Thus a drop in gross hash
My fault, this time i was talking about cpu. 70% was referred to the cpu. Btw i ordered an i5 and should be delivered next week.. i will update my results
Regarding you, i think your main reason why the first instance lose power is due cpu. Which cpu are you using? and or curiosity, how much ram?
Lol I meant on my i5 I got 4 x 70% cpu usage on its 4 cpu cores with 1 instance of the miner. When i went to 2 instances total cpu usage went to 4 x100%. I.e full cpu maxed out on two instances with no increase in hash.
4gb syatem ram. Simple miner on usb. I have an i7 I could pop in and try
Well, consider that 4 gb of ram is not enough to make multi instances (3) to work properly (swap is not helping so much)... My suggestion is: try putting 8 gb of ram, hiveos and the i7 you mentioned above, after that open three instances