System requirements for AirControl?

[pchOlkin]

Can any body tell me system requirements for AirControl stable work?

[UBNT-Thomas]

Depends on the number of managed devices. For 100 devices I would recommend to put AirControl on a server machine with 2-3 GB physical memory and dual-core CPU, running Linux or server flavor of Windows. AirControl process should have between 512 MB - 1GB physical memory available and no other CPU hogs run on the box. Would be great if folks can share what they are using for decent performance with respective managed device count.

[pchOlkin]

Depends on the number of managed devices. For 100 devices I would recommend to put AirControl on a server machine with 2-3 GB physical memory and dual-core CPU, running Linux or server flavor of Windows. AirControl process should have between 512 MB - 1GB physical memory available and no other CPU hogs run on the box. Would be great if folks can share what they are using for decent performance with respective managed device count.

Thanks! But I have over 500 devices, and that is why my test PC (1.5 Ghz Celeron with 512 RAM) was overload when I try to manage all that devices :))))))))))))

[Sirhc]

220 Devices and climbing
2.66 Core 2 Duo
4 Gigs Ram
Windows XP Pro

Seems fine. CPU spikes to 40%

[ncrossley]

50 devices
Intel Corei7 920 @ 3.6GHz
12GB RAM
Ubuntu Server 9.10

I don't think my CPU spiked 1% lol

[rconaway]

I just found that with a dual-processor XEON with 1GB of ram, 150 devices works great.

[lncommunications]

Our test rig under NAT reporting conditions...

http://www.freetheinternet.org/ubnt/ac_xp_server_thumb.jpg (http://www.freetheinternet.org/ubnt/ac_xp_server.jpg)

Click on thumb for full screenshot.

[treichhart]

would:
Gigabyte MA785GM-US2H Motherboard & AMD Phenom X4 9750 Quad Core Processor
with 4GB of memory and
160 GB sata hard drive
running ubuntu 9.10 server

be enough to run over 200 devices?

[UBNT-Thomas]

Yes, with room to the upside. How much processing takes place mostly depends on the frequency of stats updates from the devices, which you can tune under Settings (default every 30 seconds as of 1.0.07). If you find the CPU utilization too high you can increase the reporting interval and timeout.