Quote from: Frz on November 13, 2013, 03:18:43 PM
I tried switching to the sphlib library for better sha512 performance, I seem to be getting about 50% more collisions per minute on my test system

I would be happy if someone could test how it affects their performance.
https://github.com/FrzMe/jhProtominer/tree/linux-port

10% more collisions on a 16 core (32 threads) machine.

Quote from: jh00 on November 12, 2013, 01:08:21 AM
Hi,

We are happy to announce our new Protoshares mining pool on ypool.net
At the same time we also release our custom miner which is up to 5 times faster than the wallet miner.

Stats:

• 150 confirmations per block (will be decreased in the future)
• Custom miner software & low latency protocol
• High performance server - Very low percentage (<0.5%) of rejected shares or miner downtime
• Active in development - New features coming every few days
• Very helpful and active community
• Payout limit 2 PTS
• 10% fee (see below)

Link:
http://ypool.net

Once registered, you can find a guide on where to download our miner and how to set it up. Currently it is only compatible with ypool and only available for Windows 32bit/64bit.

Why is the fee so high?
I spent a lot of time on developing the miner. Instead of selling the miner or keeping it for myself I decided to publish it (including source). You can see the higher fee as a way of donating some additional coins for my effort. However, the major speed advantage you have by using this miner will make easily up for it. Not only is it a lot faster, it also uses a different algorithm that allows to use a customizable size of memory per thread. Currently you can choose between 8, 32, 128, 256 and 512 megabytes of memory per thread. If you choose more the miner will be faster, but if you have a few low-memory machines lying around this will now allow you to use them for Protoshares mining.

The source of the miner will be available on github soon.


-- jh00 & testix

so how about it? does using more memory help? if it does, please recompile a miner that can go as high as 16GB per thread

Quote from: Buratino on November 13, 2013, 02:10:41 PM

Quote from: barwizi on November 13, 2013, 02:02:59 PM
hi, would i get better results if i allocate more memory? currently using 512mb, but i can go as higher

No, it hardcoded into original source code miner.

I see only these switches:
#define PROTOSHARE_MEM_512      (0)
#define PROTOSHARE_MEM_256      (1)
#define PROTOSHARE_MEM_128      (2)
#define PROTOSHARE_MEM_32      (3)
#define PROTOSHARE_MEM_8      (4)

UPD. I agree with tyeken8.

i'd need a windows build though

I tried switching to the sphlib library for better sha512 performance, I seem to be getting about 50% more collisions per minute on my test system

I would be happy if someone could test how it affects their performance.
https://github.com/FrzMe/jhProtominer/tree/linux-port

Are your miners connecting?

Quote from: joesmoe on November 13, 2013, 03:09:51 PM
Can't seem to load the website, is the pool being ddossed or something?

I have the same problem right now.

Can't seem to load the website, is the pool being ddossed or something?

Quote from: Buratino on November 13, 2013, 03:02:43 PM

Quote from: Proto on November 13, 2013, 02:40:58 PM
Woha. Ypool now has coll/m: 1495296.00 and 50000 connected workers.

Actually that's very bad for Protoshares. Look at the overall stats. Looks like Ypool finds nearly every block there is and could pull off a 50% attack with ease. I know, there is no reason he should do it, because the 6% fee is quite lucrative and he will protect his investment. But still that is fundamentally not good for a crypto currency.

We need a solo miner with similar performance to level out the playing field and make this a decentralised currency again!

You are right!

We need external miner for Protoshares-Qt like ypool miner or private custom pool.

well it's not so hard, expecting someone to write it

Quote from: Proto on November 13, 2013, 02:40:58 PM
Woha. Ypool now has coll/m: 1495296.00 and 50000 connected workers.

Actually that's very bad for Protoshares. Look at the overall stats. Looks like Ypool finds nearly every block there is and could pull off a 50% attack with ease. I know, there is no reason he should do it, because the 6% fee is quite lucrative and he will protect his investment. But still that is fundamentally not good for a crypto currency.

We need a solo miner with similar performance to level out the playing field and make this a decentralised currency again!

You are right!

We need external miner for Protoshares-Qt like ypool miner or private custom pool.

Quote from: favdesu on November 13, 2013, 02:49:49 PM
Waiting for payout:

BALANCE (PTS)
2.80319504

haha, ayase chan. I use your avatar as a emoticon in my daily chatting. ww

Waiting for payout:

BALANCE (PTS)
2.80319504

Woha. Ypool now has coll/m: 1495296.00 and 50000 connected workers.

Actually that's very bad for Protoshares. Look at the overall stats. Looks like Ypool finds nearly every block there is and could pull off a 50% attack with ease. I know, there is no reason he should do it, because the 6% fee is quite lucrative and he will protect his investment. But still that is fundamentally not good for a crypto currency.

We need a solo miner with similar performance to level out the playing field and make this a decentralised currency again!

Quote from: barwizi on November 13, 2013, 02:02:59 PM
hi, would i get better results if i allocate more memory? currently using 512mb, but i can go as higher

No, it hardcoded into original source code miner.

I see only these switches:
#define PROTOSHARE_MEM_512      (0)
#define PROTOSHARE_MEM_256      (1)
#define PROTOSHARE_MEM_128      (2)
#define PROTOSHARE_MEM_32      (3)
#define PROTOSHARE_MEM_8      (4)

UPD. I agree with tyeken8.

Quote from: mmx888 on November 13, 2013, 01:51:48 PM

Quote from: jh00 on November 12, 2013, 03:04:23 PM
Sorry for the downtime. There was a ddos attack a few days ago which forced us to migrate to new software/hardware immediately to withstand the attack, it worked but the downside is that the service is a bit unstable now. Yesterday I found a very critical bug that probably has caused a majority of the crashes. Since it was fixed there has not been a single second of downtime caused by our own software. The recent 5 hour downtime was due to a hard disk failure, which is just bad luck and it was also the only time since the launch of our pool where the pool server for mining was down and not only the fronted.

Again I am sorry for the inconvenience.

The good news is that we have ~5000 workers connected and find a block every 6 minutes, not bad for a pool that is up for only 18 hours.

HI,jh00
how to set 1024 megabytes of memory per thread?
pls help me
THX.

merge my master branch, that one has 1024, 2048 and 4096 MB options

Quote from: mmx888 on November 13, 2013, 01:51:48 PM

Quote from: jh00 on November 12, 2013, 03:04:23 PM
Sorry for the downtime. There was a ddos attack a few days ago which forced us to migrate to new software/hardware immediately to withstand the attack, it worked but the downside is that the service is a bit unstable now. Yesterday I found a very critical bug that probably has caused a majority of the crashes. Since it was fixed there has not been a single second of downtime caused by our own software. The recent 5 hour downtime was due to a hard disk failure, which is just bad luck and it was also the only time since the launch of our pool where the pool server for mining was down and not only the fronted.

Again I am sorry for the inconvenience.

The good news is that we have ~5000 workers connected and find a block every 6 minutes, not bad for a pool that is up for only 18 hours.

HI,jh00
how to set 1024 megabytes of memory per thread?
pls help me
THX.

hi, would i get better results if i allocate more memory? currently using 512mb, but i can go as higher