M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner

[mdude77]

If you're using the latest beta, and the ant grid is the wrong size again, please redownload.  It changed sizes of it's own accord again.

M

[mdude77]

Here's hoping the next release is geared towards me ;-p

Your change requires a bit of reworking my code.  I intend to address your issues when I redo the UI for config.

M

[kgb2mining]

Matt, I'm not sure the biggest performance issue here is the actual polling of the Ants ... I think it might be the drawing of the status table.

So I was testing out the new beta with the thread slider on a 2 vCPU Win7 VM against 54 Ants (mixed S1/S3).  Testing results while viewing the status window on "Ants" tab showed:

1 thread - ~35s
2 - 3 threads - ~20s
4+ threads - ~10s
From 4 to 64 threads there was no difference in performance.

While I was playing around with the different thread values, I initiated a manual refresh while still on the "Config" tab accidently, not switching back to the status grid before doing the refresh.  While on that tab:

1 - 3 threads - ~6s
4 - 8 threads - ~5s
12 threads - ~4s
32 threads - 64 threads - ~2s

It was amazing the performance difference when not on the "Ants" tab showing the status grid.

Not sure how your logic is done, but are you waiting for the return of the values for the Ant per thread and drawing each one at the end of the thread before moving to the next?  If so it might make sense to do the poll in the background, write the info to an output area, maybe a file, and then you can generate the status table from there.  Either way it may be limited by the graphics processing part of this.

Now, I'm on a VM, which has crappy video performance in general being that it's a VM and meant for server purposes, not high end resolutions and performance.  Maybe that has something to do with it but I don't have a regular machine with a good video card to test it that way yet.  Could do on Tuesday with my laptop.

[mdude77]

Matt, I'm not sure the biggest performance issue here is the actual polling of the Ants ... I think it might be the drawing of the status table.

So I was testing out the new beta with the thread slider on a 2 vCPU Win7 VM against 54 Ants (mixed S1/S3).  Testing results while viewing the status window on "Ants" tab showed:

1 thread - ~35s
2 - 3 threads - ~20s
4+ threads - ~10s
From 4 to 64 threads there was no difference in performance.

While I was playing around with the different thread values, I initiated a manual refresh while still on the "Config" tab accidently, not switching back to the status grid before doing the refresh.  While on that tab:

1 - 3 threads - ~6s
4 - 8 threads - ~5s
12 threads - ~4s
32 threads - 64 threads - ~2s

It was amazing the performance difference when not on the "Ants" tab showing the status grid.

Not sure how your logic is done, but are you waiting for the return of the values for the Ant per thread and drawing each one at the end of the thread before moving to the next?  If so it might make sense to do the poll in the background, write the info to an output area, maybe a file, and then you can generate the status table from there.  Either way it may be limited by the graphics processing part of this.

Now, I'm on a VM, which has crappy video performance in general being that it's a VM and meant for server purposes, not high end resolutions and performance.  Maybe that has something to do with it but I don't have a regular machine with a good video card to test it that way yet.  Could do on Tuesday with my laptop.

That's an interesting test and results.  I am purposely rendering the grid after each one returns, as there could be situations where if I wait for them all to return, it'd never refresh.  (Say a few aren't responding, or the refresh rate is so low that it restarts before it's finished.)

That said, I don't have to *instantly* refresh the grid.  I'll make a minor tweak that will slow down the refreshing of the grid, but it'll still be fast enough to appear to be pretty quick.  In your situation it should speed things up.

Thanks!

M

[mdude77]

Here's another beta.  This version fixes a few things, including re-enabling the web scraping code.  I don't think there's any gain to the web scrapers in this code, but it works again.

I also added a configurable "display refresh" delay the defaults to 1 second.  That's how long the display holds off refreshing from the time an Ant refresh is initiated.  Users with slow video or large numbers of Ants will benefit from making this value larger. 

For example, when set to '1', every Ant that refreshes in the first second will refresh on the grid at once.  Every Ant that hasn't yet responded, or hasn't yet been refreshed, will show up automatically as it's refreshed.  Using the test results posted earlier, where it took 5 seconds to refresh 50 Ants when the grid wasn't shown, if you set it to 5 seconds, most if not all should refresh after 5 seconds.

This is pretty close to the final build for this version number.

As always, feedback is welcome and appreciated.

Download link: MAntMonitor32b2.zip

M

[dogie]

Thread has been moved to mining software.

[hendrigo]

Hi Mdude77,
This is great software and almost perfect.

The only thing needed is for it to auto reboot the miner when the S1 is losing intenet connection
and showing as ERROR on Ant Uptime. at this time, miner is still can be access by web interface.

My miner is connected by wifi and everyday my internet provider reboot their wireless connection
at 2 AM, after internet is back, some of my S1 will not hashing until I do reboot after wake up.

Please help to enable option to auto reboot miner that showing ERROR on uptime.

Cheers and Thank's

[mdude77]

Hi Mdude77,
This is great software and almost perfect.

The only thing needed is for it to auto reboot the miner when the S1 is losing intenet connection
and showing as ERROR on Ant Uptime. at this time, miner is still can be access by web interface.

My miner is connected by wifi and everyday my internet provider reboot their wireless connection
at 2 AM, after internet is back, some of my S1 will not hashing until I do reboot after wake up.

Please help to enable option to auto reboot miner that showing ERROR on uptime.

Cheers and Thank's

Hi, thanks!  This should be quite doable.  Look for it in the next version.

M

[kgb2mining]

Here's another beta.  This version fixes a few things, including re-enabling the web scraping code.  I don't think there's any gain to the web scrapers in this code, but it works again.

I also added a configurable "display refresh" delay the defaults to 1 second.  That's how long the display holds off refreshing from the time an Ant refresh is initiated.  Users with slow video or large numbers of Ants will benefit from making this value larger. 

For example, when set to '1', every Ant that refreshes in the first second will refresh on the grid at once.  Every Ant that hasn't yet responded, or hasn't yet been refreshed, will show up automatically as it's refreshed.  Using the test results posted earlier, where it took 5 seconds to refresh 50 Ants when the grid wasn't shown, if you set it to 5 seconds, most if not all should refresh after 5 seconds.

This is pretty close to the final build for this version number.

As always, feedback is welcome and appreciated.

Download link: MAntMonitor32b2.zip

M

W00t!  That change made a big improvement.

First off, the best performance I could get was 2s, no matter the max threads or display refresh setting.  I'm thinking I just don't have enough ants yet to really stress it out too much   We'll see what happens with the dude with 1,000 Ants.

With 2s or above display refresh setting, on "Ant" tab or any other:
4 threads - 10s
6 threads - 6s
8 threads - 4s
12 threads - 2-3s
16+ threads - 2s

So, changing the refresh default even by 1s made the main difference, the table draws nice and quick and it doesn't matter what tab you're on now, performance is consistent.  Anything above 2s really made no difference, again I think you'd need probably 150+ Ants to get into that territory.

Great work!

[mdude77]

Here's another beta.  This version fixes a few things, including re-enabling the web scraping code.  I don't think there's any gain to the web scrapers in this code, but it works again.

I also added a configurable "display refresh" delay the defaults to 1 second.  That's how long the display holds off refreshing from the time an Ant refresh is initiated.  Users with slow video or large numbers of Ants will benefit from making this value larger. 

For example, when set to '1', every Ant that refreshes in the first second will refresh on the grid at once.  Every Ant that hasn't yet responded, or hasn't yet been refreshed, will show up automatically as it's refreshed.  Using the test results posted earlier, where it took 5 seconds to refresh 50 Ants when the grid wasn't shown, if you set it to 5 seconds, most if not all should refresh after 5 seconds.

This is pretty close to the final build for this version number.

As always, feedback is welcome and appreciated.

Download link: MAntMonitor32b2.zip

M

W00t!  That change made a big improvement.

First off, the best performance I could get was 2s, no matter the max threads or display refresh setting.  I'm thinking I just don't have enough ants yet to really stress it out too much   We'll see what happens with the dude with 1,000 Ants.

With 2s or above display refresh setting, on "Ant" tab or any other:
4 threads - 10s
6 threads - 6s
8 threads - 4s
12 threads - 2-3s
16+ threads - 2s

So, changing the refresh default even by 1s made the main difference, the table draws nice and quick and it doesn't matter what tab you're on now, performance is consistent.  Anything above 2s really made no difference, again I think you'd need probably 150+ Ants to get into that territory.

Great work!

Woohoo!  2s for 50 Ants!  Sweet!

M

[hendrigo]

Hi Mdude77,
This is great software and almost perfect.

The only thing needed is for it to auto reboot the miner when the S1 is losing intenet connection
and showing as ERROR on Ant Uptime. at this time, miner is still can be access by web interface.

My miner is connected by wifi and everyday my internet provider reboot their wireless connection
at 2 AM, after internet is back, some of my S1 will not hashing until I do reboot after wake up.

Please help to enable option to auto reboot miner that showing ERROR on uptime.

Cheers and Thank's

Hi, thanks!  This should be quite doable.  Look for it in the next version.

M

Hi Mdude77,

See this link of the ERROR on uptime and the log provide by v3.2b2

http://tinypic.com/r/jai9nc/8

Thank's

[mdude77]

Hi Mdude77,

See this link of the ERROR on uptime and the log provide by v3.2b2

http://tinypic.com/r/jai9nc/8

Thank's

That is not what I expected.  You're saying it's accessible via the web, but not via the API?  In other words, you need it to rebooted via the web when this happens, not the API.

M

[hendrigo]

Hi Mdude77,

See this link of the ERROR on uptime and the log provide by v3.2b2

http://tinypic.com/r/jai9nc/8

Thank's

That is not what I expected.  You're saying it's accessible via the web, but not via the API?  In other words, you need it to rebooted via the web when this happens, not the API.

M

When ERROR appear, I still can use Ant Monitor to reboot it by use API setting.

[mdude77]

Hi Mdude77,

See this link of the ERROR on uptime and the log provide by v3.2b2

http://tinypic.com/r/jai9nc/8

Thank's

That is not what I expected.  You're saying it's accessible via the web, but not via the API?  In other words, you need it to rebooted via the web when this happens, not the API.

M

When ERROR appear, I still can use Ant Monitor to reboot it by use API setting.

Okay.  For now I have it written to use web reboot if the API fails.

M

[mdude77]

Version 3.2 release candidate is now available.

MoreBloodWine: You might want to try this one.  It still won't save properly for you, but I think reboots will work for you now.  The web code is cleaner as well.

This also includes the ability to attempt to reboot an Ant via the web if the API call generates an error.

MAntMonitor32rc.zip

M

[hendrigo]

Version 3.2 release candidate is now available.

MoreBloodWine: You might want to try this one.  It still won't save properly for you, but I think reboots will work for you now.  The web code is cleaner as well.

This also includes the ability to attempt to reboot an Ant via the web if the API call generates an error.

MAntMonitor32rc.zip

M

Hi M,
The 3.2rc did try to gp web based reboot, but unable. below the log:

9/1/2014 11:09:50 PM: ERROR when querying S1:2.117:80 (step 1): Object reference not set to an instance of an object.
9/1/2014 11:09:50 PM: Attempting to reboot S1: 192.168.2.117:80 via the web because the API query errored out.
9/1/2014 11:09:50 PM: REBOOTING S1: 192.168.2.117:80
9/1/2014 11:09:53 PM: An error occurred when parsing the web output for http://192.168.2.117/cgi-bin/luci/;stok=/admin/system/reboot?reboot=1: Object reference not set to an instance of an object.

[wlz2011]

Here's a beta version of 3.2.  The huge change to this was it was restructured to do multi-threaded polling of your Ants via the API.

Things to note:

- This is a beta version.  Chances are good I broke something.  
- That said, you should be able to revert back to the prior version simply by running the older version.
- This is for API users only.  I'm pretty sure the web scraping piece is broken, simply because I haven't taken the time yet to redo it to work with the new code.
- It has 5 threads running behind the scenes: 1 dispatch thread, and 4 worker threads.  I intend to have the worker threadcount controllable in the final version.
- You'll see in the Log which worker thread is checking which Ant.
- My main PC is an i7.  That means have 4 CPU cores with hyperthreading, so the OS sees 8 cores available.  I don't know how this will respond on CPUs with less cores available.  
- I only have 3 Ants: 1 S1, 1 S2, and 1 S3.  I can't really test how this will work with more than 3 Ants, especially not 1000.

As always, feedback is most welcome.

Thanks!

Download link: MAntMonitor32b.zip

M

Beta 3.2b

253 ants scan time = 95 seconds

Speed ​​increased 3.5-4.0 times.

No multi-segment scan.

No test 3 digit IP (192.168.001.002 - 001.253) sorted the problem, the problem actually is not too important.


3.2b1 has not been tested

Thank you been trying to work.

Google Translation

[mdude77]

Hi M,
The 3.2rc did try to gp web based reboot, but unable. below the log:

9/1/2014 11:09:50 PM: ERROR when querying S1:2.117:80 (step 1): Object reference not set to an instance of an object.
9/1/2014 11:09:50 PM: Attempting to reboot S1: 192.168.2.117:80 via the web because the API query errored out.
9/1/2014 11:09:50 PM: REBOOTING S1: 192.168.2.117:80
9/1/2014 11:09:53 PM: An error occurred when parsing the web output for http://192.168.2.117/cgi-bin/luci/;stok=/admin/system/reboot?reboot=1: Object reference not set to an instance of an object.

That first error message is curious.  You say that goes away after you reboot it?

M

[mdude77]

Beta 3.2b

253 ants scan time = 95 seconds

Speed ​​increased 3.5-4.0 times.

No multi-segment scan.

No test 3 digit IP (192.168.001.002 - 001.253) sorted the problem, the problem actually is not too important.

Please try the latest version: MAntMonitor32rc2.zip

I suggest setting the display refresh value to 5 and the thread count to at least 24.

M

[mdude77]

Release candidate #2.

MAntMonitor32rc2.zip

Only thing different is for the "reboot on error out" it uses the API to try to reboot instead of the web browser.

M