Multi-Rig MONA Hashrate

After the wallet name, put a period and then an arbitrary name for the computer for you to identity. I have mine set up with the old service tags - wallet id = xxxxxxx."service tag number"

From the section on mining in the site:

• If you are mining on multiple machines/rigs, you can append an identifier of your choice to your wallet address separated by a dot to make it easier to distinguish between your rigs when evaluating your results. Example: <WALLET ADDRESS>#<OPTIONAL PAYMENT_ID>.<OPTIONAL WORKERNAME>

Thank you Marty. From the client, it returns a rate of about 130 MH per rig, but the website shows between 30 and 40 for each one.  I know there is usually a discrepancy between the two, this just seems like a fairly large gap. 

Comrade-in-arms, let me give you some reference. I'm using an overclocked MSI Geforce GTX 1080 Ti, From the client of my computer, it shows 74.89 MH/s, on the website of poolmining.org shows from 22.8 MH/s to 27.9 MH/s to 33.1 MH/s to 46.9 MH/s to 69 MH/s, theoretically it's impossible to reach the speed number on your computer, it's fluctuating without a fixed one. At the begining of mining here, I've calculated shares produced for 24 hours by setting an alarm clock, 7371 shares. And at that time, I didn't overclock to this level 74.89 MH/s. So I'm not clear, how about the speed of shares now.

Our mining pool members are increasing crazily, when I was mining here sometime's  before, only 18 miners to mine together with less than 700 MH/s, and boss was frustrating for low hashrate to find a block. The crowd is mobbing in now. If you have the interest you could find it in the old post, and I was encouraging him: "No matter a big or small pool right now". Interesting to mine here. (≧▽≦)

Do you guys know which port I should use if I'm using 2 computers to mine, a personal desktop with 1x 1070 that I'm mining with, as well as a separate rig with 3x 1070s I'm mining with also for Mona?

On a side note, how long do the payouts take? There is an 11 hour old block with 0% status still. 

I'm interested in the 0% status as well - it looks like there are 4 blocks all at 0%...

The daemon got stuck overnight. Should be fine now.