@gsrcrxsi / high rejection rate:
on v0.7: i'm currently experiencing this on my own, it looks like the rejects are coming in "chunks" with 5-6 rejects in a row, then everything is fine again.
is this was you're seeing too?

i don't have a hint right now what's the cause, i'll have to dig deeper through the server logs / mining code 

/edit: and i just got home, i'll check the code now.

@cjrhoades / afr33sl4ve:
this is getting a little confusing, so you're using v0.5 and v0.7 ? both with the same problem.
and both of you encounter the "collision found" but -no- "submitted share -> <whatever>" line in the miner output?

if this happens and you dont see enough shares in the last blocks (user stats), then it looks like the submission is not reaching the server, thus you don't get an answer from the server about your submitted share. the miner itself counts every share that has been submitted regardless of the/an answer from the server about that submission.

also please be aware, that your most recent shares are currently not shown in the user stats, as these are bound to found blocks, and the last found blocks is 2.5 hours old

- xolokram

if
[MASTER] submitted share -> SHAREis missing, then you didnt receive the answer of the pool
the submission is executed with the
collision foundline

- xolokram

ps. letme check the server, this and the very high blocktime are strange

/edit:
ok, if you ask me someone's trying to fu-- up the pool (or is using a totally broken status update script)
more than 5k connections on port 80 while 4k miners are connected...

i had 1-2% on one machine and 4-6% on other machines yesterday

i would say 15% is too much

can you PM me a part of your console output of the miner with some information about REJECTED shares?

- xolokram

can someone on a i7 with SSE4 but -NO- AVX check if replacing
-march=native
with
-march=corei7
in
makefile.unix

then compile, then run, helps?

- xolokram

ps. sorry, i'm currently not able to test is

newest experimental v0.7 needs yasm to be installed for compilation
and it looks like that avx/sse4 is disabled on (all? some?) digitalocean vps machines

CPU?

btw i added a "known issues" information to the original miner update post, so we dont have to repeat everything

- xolokram

maybe update for v0.7
requiring yasm for compilation

- xolokram

ps. see http://bitsharestalk.org/index.php?topic=234.msg9657#msg9657

/edit1:
 

/edit2: i will just re-use this post

new ptsminer v0.7 EXPERIMENTAL/TOO LATE?/BEEEEER EDITION *UPDATED-#3*
for ptsweb.beeeeer.org & #beeeeer.org @ Freenode

linux / github: source code here
windows binary: v0.7 x64 RC1 -> ptsminer_v07b_x64.zip (64 Bit, experimental, fastererer™!!!!!!) *updated-#3* incl. 'rejections-on-a-block-workaround-by-reconnecting'-fix
(containing GENERIC (INTEL&AMD) , SSE4 and AVX version (INTEL&AMD))

new optional parameter, check the usage example below

• AVX / SSE support (thx to glitchboy)
• SPHLIB support
• RAM option (new parameter!)
• smaller rejection problem bugfix
• reduced thread priority of worker-thread

choose <version> depending on your CPU and mining implementation you want to use

usage: ptsminer_<version>.exe <payout-address> <threads-to-use> [memory-option] [mode]

memory-option: integer value - memory usage
                20 -->    4 MB per thread (not recommended)
                21 -->    8 MB per thread (not recommended)
                22 -->   16 MB per thread (not recommended)
                23 -->   32 MB per thread (not recommended)
                24 -->   64 MB per thread (not recommended)
                25 -->  128 MB per thread
                26 -->  256 MB per thread
                27 -->  512 MB per thread (default)
                28 --> 1024 MB per thread
                29 --> 2048 MB per thread
                30 --> 4096 MB per thread

mode: string - mining implementation
                avx --> use AVX (ptsminer_avx.exe)
                sse4 --> use SSE4 (ptsminer_avx_*.exe & ptsminer_sse4.exe)
                sph --> use SPHLIB (ptsminer_avx_*.exe, ptsminer_sse4.exe, ptsminer_amd.exe & ptsminer_intel.exe)


examples:
ptsminer_avx.exe PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 4
using AVX on 4 threads and 512 MByte RAM per thread (default)

ptsminer_sse4.exe PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 8 28
using SSE4 on 8 threads and 1024 MByte RAM per thread

ptsminer_intel.exe PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 2 25 sph
using SPHLIB on 2 threads and 128 MByte RAM per thread

ptsminer_avx.exe PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 12 24 sph
using SPHLIB on 12 threads and 64 MByte RAM per thread

build notes:

boost library & YASM required for compilation!

currently the mode parameter has to be set manually on linux machines (fix will come later), no autodetection atm

sudo apt-get install yasm
i expect some problems with the compilation as i've not tested the miner on every linux / mingw distrubution out there... be patient, dont panic

compiler warnings on the SPHLIB files are alright (incl. sph_sha2.c, sph_sha2big.c & md_helper.c)

and next difficulty coming in fast...

problems with compilation? adapt some of the things from --> HERE (thanks to donschoe, don't forget to DONATE!!)

I can't test on OSX. Maybe someone can say if the compilation works on OSX??

KNOWN ISSUES:
1) on Amazon EC2 instances AVX is permitted (?!?) --> the miner crashs <-- SSE version is working fine, you'll have to set SSE4 mode manually
2) OSX compilation errors due to byteswap & *i-forgot-urghs* thread priority(?)

todo:

• abandoned addresses payout script
• fix that bug "crashing after share submission" on windows
• add option to choose mining code optimization manually (avx,sse,sphlib)

- xolokram

ps. cmake file is not up-to-date, i will fix that asap
pps. using 32 bit linux distribution could be problematic... will look into that later
note --- quick dirty 32 bit linux distribution workaround: replace "elf64" in makefile.unix by "elf"