Changing the hashing algorithm

Tuck Fheman

it’s a shame rate of release can’t be tied to some form of community health indicator. But I guess there isn’t one that would be suitable or reliable.

Not exactly what you’re looking for I’m sure, but I use Coingecko as a “community health indicator”.

tmuir12

Interesting, but I can even that could be manipulated to get you up the ladder, as it also takes into account the number of followers on twitter, and facebook which is easily upped by making fake accounts, same with followers on github.

Same with people could make forks of the code, to raise its status, liquidity is a good stat though

Lukey_p

Hi, i have downloaded the testnet and i am currently solomining with my CPU, is this all you need for testing? is there anything else we can do?

I take it these coins are pointless mining, just for testing, shame huh!

ghostlander

Hi, i have downloaded the testnet and i am currently solomining with my CPU, is this all you need for testing? is there anything else we can do?
I take it these coins are pointless mining, just for testing, shame huh!

These testnet coins are of no value indeed. You can post your CPU model and hash rate (wallet / CPUminer).

Lukey_p

Im using my work Laptop and the wallet in the link above, 0.6.6.0 and solo mining.

using 3/4 cores of an i3-2310M and getting exactly 3000 hashes per second good sir.

ChekaZ

Ive got 14.3kh/s on Intel® Core™ i5-3570K CPU @3.40GHz

Fiftysven

I got 24.3kh/s on IntelÂ® Coreâ„¢ i7-3770K CPU @ 3.50 GHz 3.90 GHz

j_scheibel

intel xeon cpu e5-2697 v2 @2.97 ghz

solo mining - kind of interesting how it degrades despite not running out of logical processors.

1 thread - 2655 h/s

2 threads - 5230 h/s

4 threads - 10kh/s

8 threads - 20 kh/s

12 threads - 30 kh/s

24 threads - 45 kh/s

32 threads - 64 kh/s

44 threads - 72 kh/s

pool mining

1 thread - 8.9kh/s

2 thread - 17.2kh/s

4 threads - 33.3 kh/s

8 threads - 67.6 kh/s

12 threads - 100 kh/s *pool miner tends to hang beyond here if I let it run for more than just a few seconds*

lizhi

Not connect http, why ?

j_scheibel

i had the same problem. no idea how to fix it though. i just used one of the 2 pools listed.

Lukey_p

intel xeon cpu e5-2697 v2 @2.97 ghz

solo mining - kind of interesting how it degrades despite not running out of logical processors.

1 thread - 2655 h/s

2 threads - 5230 h/s

4 threads - 10kh/s

8 threads - 20 kh/s

12 threads - 30 kh/s

24 threads - 45 kh/s

32 threads - 64 kh/s

44 threads - 72 kh/s

pool mining

1 thread - 8.9kh/s

2 thread - 17.2kh/s

4 threads - 33.3 kh/s

8 threads - 67.6 kh/s

12 threads - 100 kh/s *pool miner tends to hang beyond here if I let it run for more than just a few seconds*

Hi, i assume you are using Hyper-V or VMware and assigning vCPUs, At a guess, i would imagine using HT cores could contend very quickly. Are you in a position to disable HT on the CPU and assign cores only? just to see if a single core gives more that 2 threads with HT on?

Just a thought.

Luke

lizhi

Yes. Blank or whatever. You can also use “Pool Mining” for solo mining (server = http://127.0.0.1, port = 19554, username and password = what you have in phoenixcoin.conf). There will be a difference in performance though.

The wallet uses the reference C code for its solo miner. CPUminer (minerd) is powered by the SSE2 assembly code. It is also used for pool mining by the wallet. Try both and report your KH/s. For example, my 3GHz 4-core A8-3870K delivers 10KH/s using the built-in miner and 8KH/s using CPUminer (yes, it’s slower in my case).

Please give me a screen-shot .

FeatherKing

I got 3.4 KH/s with 2 threads on I3-2330 2.2 GHz at pool mining.

lizhi

Intel G2020 CPU 3.1G is6.5Kh.

Lukey_p

So, i have a question… When the move is complete, do we think CPU mining will actually be viable? Is CPU mining going to be exclusive for a while before GPU? If GPU mining neoscrypt is working on release, will anyone actually use CPU?

Just throwing it out there, be nice to have an idea, Cheers

ghostlander

Not connect http, why ?

Maybe add rpcallowip=127.0.0.1, rpcuser=lizhi and rpcpassword=123 to data/testnet/phoenixcoin.conf?

j_scheibel

Hi, i assume you are using Hyper-V or VMware and assigning vCPUs, At a guess, i would imagine using HT cores could contend very quickly. Are you in a position to disable HT on the CPU and assign cores only? just to see if a single core gives more that 2 threads with HT on?

Just a thought.

Luke

I wasn’t using any kind of virtual machine. I could go in to the bios and turn off the hyper threading but I can’t imagine that helping overall since you cut the overall power by half. I probably wont be in front of the computer to play with it for a day or so, regardless, I really expect this was more of a bottleneck imposed by the managing process (ie the wallet). I mean the wallet had locking issues when using pool settings with 12 or more threads . so there might be some bugs in there. however, the underlining code that does the new scrypt seems to be running ok though. (which I thought was the point of the test :) )

mirrax

I don’t know if Lizhi is successfull with modification of cgminer?

But now two scenarios trouble me a little:

1st, botnets targeting Neoscrypt in CPU era

2nd, if first GPU miner will be private

Is this valid lamentation or not much?

lizhi

Hi guys, I’m still not successful . I was caught in the kernel . I refer to the KECCAK, try to write some code. But no progress. :'(

I cannot write similar code for Nerscrypt in driver-opencl.c and ocl.c

#ifdef USE_KECCAK
static cl_int queue_keccak_kernel(_clState *clState, dev_blk_ctx *blk, __maybe_unused cl_uint threads)
{
        cl_kernel *kernel = &clState->kernel;
        unsigned int num = 0;
        cl_int status = 0;

        status = clEnqueueWriteBuffer(clState->commandQueue,
                clState->keccak_CLbuffer, true, 0,
                KECCAK_BUFFER_SIZE, &blk->keccak_data[0],
                0, NULL,NULL);

        CL_SET_ARG(clState->keccak_CLbuffer);
        CL_SET_ARG(clState->outputBuffer);

        return status;
}
#endif

The biggest difficulty is to write neoscrypt140707.cl, This is a binary code .

		case KL_NEOSCRYPT:
			strcpy(filename, NEOSCRYPT_KERNNAME".cl");
			strcpy(binaryfilename, NEOSCRYPT_KERNNAME);
			/* Neoscrypt only supports vector 1 */
			cgpu->vwidth = 1;
			break;

lizhi

This is my project, It comes from cgminer 3.6.6

How to build:

cd /D/FTC/neoscrypt/max-cgminer-master

autoreconf -fvi

export LIBCURL_CFLAGS=-I/usr/local/curl/include

export LIBCURL_LIBS=-L/usr/local/curl/lib

CFLAGS=“-O2 -msse2” ./configure --enable-scrypt --enable-keccak --enable-neoscrypt

make

if have error information "undefined reference to `_imp__curl_easy_init’ "

you edit Makefile file , add " LIBS = -lpdcurses -lpthread -lcurl -lcurldll "