What does this sentence mean ?

the memory access will be your bottleneck

I see this everywhere but it doesn't make sense to me. What is the unit of memory access, where do you find that information ?

Quote from: r05 on December 11, 2013, 08:07:58 PM

Quote from: Harvester on December 11, 2013, 03:51:37 PM
Last question about ram influence on mining results. Is it better to use maximum amount? It's obvious to me.. but better asking :D

I've actually got lower performance by using the 1024mb option over the 512mb option. No idea why - there doesn't seem to be any clear correlation to me..

It is because you are above your max RAM amount so your system is using cache to balance.

Quote from: ahpigsy on December 12, 2013, 08:25:26 AM

Quote from: kqah5 on December 12, 2013, 06:30:58 AM
hi, i used this miner (jhprotominer-yvg1900-M7h) with ypool.net ->  ~200c/m
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
when i used ptsminer_v07b_x64 in this topic with ptsweb.beeeeer.org ->  ~170c/m.
I tried to configure jhprotominer-yvg1900-M7h with ptsweb.beeeeer.org, but i got the message " can't connect to "
anyone know how to make jhprotominer-yvg1900-M7h work with beeeeeer.org ?

I too use jhprotominer at ypool but I find beeeer.org finds a lot more shares and the block yield is a lot higher here too. About twice as much.

It is possible that the two miners have different calculation of the collisions. What matter is how much ProtoShares you get in 24 hours.

Quote from: kqah5 on December 12, 2013, 06:30:58 AM
hi, i used this miner (jhprotominer-yvg1900-M7h) with ypool.net ->  ~200c/m
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
when i used ptsminer_v07b_x64 in this topic with ptsweb.beeeeer.org ->  ~170c/m.

I tried to configure jhprotominer-yvg1900-M7h with ptsweb.beeeeer.org, but i got the message " can't connect to "
anyone know how to make jhprotominer-yvg1900-M7h work with beeeeeer.org ?

I too use jhprotominer at ypool but I find beeeer.org finds a lot more shares and the block yield is a lot higher here too. About twice as much.

actually i'll try to switch to the 'getblocktemplate' protocol completely
that means proxy & jhProtominer (afaik) should be possible without problems

(i shouldn't use the words "without problems" for upcoming features :D )

- xolokram

Quote from: mmx888 on November 15, 2013, 02:29:07 AM
HI,xolokram.
pls help me ,v0.5a how to set proxy mining?
thanks!

HI,xolokram.
I hope to set proxy mining, too.
Do you plan to implement it?

it's not possible to use jhprotominer at beeeeer's pool atm due to different communication protocols
i plan to support it, until then you'll have to stick to beeeeer's ptsminer

- xolokram

hi, i used this miner (jhprotominer-yvg1900-M7h) with ypool.net ->  ~200c/m
https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
when i used ptsminer_v07b_x64 in this topic with ptsweb.beeeeer.org ->  ~170c/m.

I tried to configure jhprotominer-yvg1900-M7h with ptsweb.beeeeer.org, but i got the message " can't connect to "
anyone know how to make jhprotominer-yvg1900-M7h work with beeeeeer.org ?

Quote from: itsfin on December 12, 2013, 02:27:04 AM
how to run on linux
I have to type in the command line?

Try this:
https://bitsharestalk.org/index.php?topic=234.msg13771#msg13771

how to run on linux
I have to type in the command line?

With my standard bat file setup just like I have on my home PC, it doesn't connect and won't mine. I opened everything up on my local firewall but I am not sure if the location I am at is blocking that port (router settings, etc), that activity, or what-not.

I had to put a flag on the wallet app to get it to connect to a node by adding it to the run command, it mined all night, supposedly, but it actually didn't do anything. Very weird. When I checked on it this morning, it had a runtime error saying it asked it to shutdown in an odd manner. I checked the log file, it didn't have a hashrate.

I really want to set up this x64 miner but the damn thing won't connect still, no matter what I do.

you cannot ping the servers

Quote from: nitrominer on December 11, 2013, 08:53:29 PM
Looks like I can't connect to 54.201.26.128 at this location. Any work around for this?

54.201.26.128 doesn't respond to pings at my location, either. Odd, because it's definitely up (miners are connecting and getting/submitting work off-site at current). Likeliness is the system the pool is sat on is just setup to reject ICMP echo requests and rather not that the server is down.

Have you tried running a miner against it, or is it just not responding to a standard ping?

Looks like I can't connect to 54.201.26.128 at this location. Any work around for this?

Quote from: xolokram on December 11, 2013, 07:34:34 PM
bottleneck for the computation

your ram/cpu is not fast enough, it's nothing unusual