1KEY Server Sizing

1KEY Server Sizing Note: This document is based on the architecture of Akira and will not be completely applicable for 1KEY 2.0.2 because 1KEY 2.0.2 works on client-server architecture and not uses server to great extend. 1KEY 2.0.2 makes call to server only for the retrieving metadata or saving metadata.

1KEY Server Sizing Akira will be complete SOA and being SOA it’s processing is distributed on these kinds of Service Servers: 1KEY Meta Server: - For storing 1KEY Repository 1KEY Web Reporting Server: - For 1KEYWeb 1KEY Scheduler Server: - For Scheduling 1KEY Web Service Server: - For 1KEY Cloud Services

1KEY Meta Server (MS)

1KEY Meta Server is mainly responsible for:

Repository

User Maintenance

Request Posting to 1KEY Web Service Server or 1KEYWeb Server

Controlling 1KEY Scheduler Server

1KEY Remoting Web Service Server (RWSS)

1KEY Remoting Web Service Server is responsible for following:

Fetching Required Data from Database Servers

Sending Request to 1KEY Client in small data packets

Storing and Retrieving metadata information to and from 1KEY Meta Server

1KEY Scheduler Server (SS)

1KEY Scheduler is responsible for following:

Scheduling of different kind of reports

Scheduling data warehousing routines

1KEY Web Reporting Server (WRS)

1KEY Web Reporting Server is responsible for following:

Executing 1KEYWebView

Executing 1KEYWebChart

Executing 1KEYWebCube

Publishing 1KEY Reports

KPI & Dashboards

Remote Reporting Access

OLAP Server (OLAPS)

OLAP Server is responsible for following:

OLAP Engine for creating cubes and reporting models.

OLAP Reporting Engine for transforming these cubes and reporting models to 1KEY’s reporting model and generate reports.

Repository User Maintenance Request Handler Scheduling Processor Data Handler Request Handler Metadata Handler Report Scheduler Data Scheduler 1KEYWebView 1KEYWebCube 1KEYWebChart KPI & Dashboards Report Publisher Report Remoteing Service Database Server WRS SS WSS MS

Repository User Maintenance Request Handler Scheduling Processor Data Handler Request Handler Metadata Handler Report Scheduler Data Scheduler 1KEYWebView 1KEYWebCube 1KEYWebChart KPI & Dashboards Report Publisher Report Remoteing Service Database Server WRS SS RWSS MS OLAP Engine OLAP Reporting Engine OLAP Server

User Calculation Total Potential Users:1000 Concurrent Active User: 10% of 1000 = 100 Simultaneous requests User Type # of Users Rate # of Requests Heavy 15 100% 15 Active 45 30% 14 Moderate 25 15% 4 Light 15 10% 2 35

Server Sizing Concurrent Users Concurrent Request Concurrent Schedules MS N - - WSS 200-300 50 20 WRS 200-300 50 - SS - 20 20 1 CPU x 4GB RAM 100 35 10 2 CPU x 8GB RAM 200 70 20 3 CPU x 16GB RAM 300 105 30

Server Sizing 1MS – For n Users 1WSS – For 200-300 concurrent active users 1SS – For 20 Schedules running concurrently 1WRS – For 200-300 concurrent active users 1CPU with 4GB RAM – For 100 concurrent users 1CPU with 4GB RAM- For 50 simultaneous requests 1 CPU with 4GB RAM – For 10 Concurrent Schedules

Variables Affecting Performance