Quote from: mdude77 on August 31, 2014, 01:55:04 AM

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

Just downloaded and tried it out. I'm using the most simplest functions of just getting status so I'm not a good measure of whether any other functionality is broken, but I am using the API and not web scraping. It definitely seems faster so far, and you can tell the refresh is working on multiples as they used to fill in one by one, now it's in groups of 4 or so just like you mentioned.

We've got 50+ Ants being monitored, and it takes about 10 seconds now to go through all of them, whereas it used to be more than double that, close to 30 seconds for a full refresh. This is on a Win7 VM with 2 vCPU's. I can bump the vCPU to 4 and see if it makes any difference as well.