Supported platforms and operating systems
The Visionect Server is distributed either as native packages for Ubuntu 14.04 LTS or as a VirtualBox virtual machine, which can be run in Windows, OSX and Linux(either with VirtualBox or Vagrant). The VirtualBox virtual machine is primary meant as a development tool, while production deployments should be done as native packages uner Ubuntu for performance reasons.
If you’re looking to run Visionect Server under other Linux distributions, then Docker is the way to go. It provides minimal overhead in environments where it is not to run Ubuntu Server natively. Official Docker support is currently in beta and Docker images are available upon request.
Memory
Server memory requirements depend on a number of factors, such as the number of devices, device type(screen size), server version, running app and update frequency.
The base system requires at least 500MB of memory for all services. Each device then require an additional 150-400MB of memory for its server session. Memory usage is tigtly connected with screen usage, so devices is not static - it shoots up during the session instantiation and then tapers down to stable state. Any memory leaks that are caused by WebKit are pevented by periodic session memory checks that restart offending processes.
Hard drive
While the Visionect Software Suite itself does not require a lot of disk space, logging facilities will be more space-consuming in the long run.
As an example, aserver which hosts 25 devices and runs a very interactive application(guests using devices to order food and drinks - alot of clicks) will generate about 4.5GB of events in six months.
Processors
As explained before, the Visionect Software Suite is mostly memory-bound. We’ve run 100 very interacitve devices in a stress test on a modern quad core processor, and it performed without any serious glitches. If your CPU utilization is very high, you’re more likely to run into issues caused by low memory and the hard drive swapping caused by it.
