NOMP npm update fail @ multihashing. about node-multi-hashing HOT 4 OPEN

Well, unfortunately, even tho the pool compiled fine and is now running ... my same config of earlier version of nomp migrated to your new version + the custom working older multihashing repo I found ... results in 15% rejects, I dont know where the bottleneck is =( ... if its the odd compile w/ pool or if its simply network related. But, back before I had to do all this ... I had about 1% rejects. I did have to update wallet daemon software , so the performance issue may be there too but doesnt seem like it. A public pool on this network w/ my miner sees about 2.5% reject, nowehere near 15% that Im experiencing ... so the network for this coin seems healthy enough. Ugh... this is discouraging.
Do u know, would there be anything in the multi-hashing that would effect reject rate? (I dont know how much that effects share / work handling and new blocks)
Watching returned shares and new blocks on nomp it seems like a good 10 seconds passes after blocknotify triggers and shares are accepted ... any shares returned by miner within those 10 seconds are rejected.

from node-multi-hashing.

Alright some more details for ya...
I pointed my forked stratum-pool to commit 18d2cbc of node-multi-hashing ... that is the latest commit in your repo that I can successfully npm update against. Any newer commit fails w/ the cryptonight compilation as outlined above.
Sadly, still insanely high reject rates =(

from node-multi-hashing.

Another quick update ...
The high rejects are not a problem w/ node-multi-hashing, turns out my hardware needed a good reseating of connections / components and now rejects are back at sub 1% normal rate.

from node-multi-hashing.

i got the same problem ...

from node-multi-hashing.