DyKnow 5.x Server Hardware Scaling Examples

Follow

Here are some examples for how you can set up your environment:

Up to 700 Licenses

  • Type: One combined DB & Application
  • Processor: DualCore
  • RAM: 8GB (4GB if less than 350 licenses)
  • Storage: Monitor only = 10GB | Monitor and Vision = 20GB (base) + 8GB per teacher

700 to 2000 Licenses

  • Type: One DB & One Application
  • Processor: DB Server = Quad Core | Application Server = DualCore
  • RAM: DB Server = 16GB | Application Server = 8GB
  • Storage: Monitor = 10GB | Monitor and Vision = 20GB (Base) + 8GB per teacher

2000 to 10,000 Licenses

  • Type: One DB & Three Application
  • Processor: DB Server = Two Quad Core | Application Server = Dual Core
  • RAM: DB Server = 32 GB | Application Server = 8GB
  • Storage: Monitor = 10GB | Monitor and Vision = 20GB (Base) + 8GB per teache

10,000+ Licenses

We have several large districts effectively supporting 10-30,000 licenses. Ask your DyKnow rep for a custom recommendation.

 

ABOUT THE CLIENT-SERVER MODEL

We use the client-server model for many reasons, but mostly because it increases network performance, is low-maintenance, and is very reliable and secure. There are three components of a client-server model:

  • CLIENT - the application (DyKnow Monitor and/or DyKnow Vision)
  • SERVER - the database (otherwise known as 'the cloud')
  • NETWORK - the communication (connects client and server)
Have more questions? Submit a request

Comments

Powered by Zendesk