To ensure optimal operation, we recommend installing the CardioLog application on a dedicated server and the CardioLog database on a dedicated SQL Server instance***.
The installer prerequisites can be found here.
Inspect the following table to assure that your system meets the minimum hardware and software requirements:
| Free/Standard Edition | Professional Edition | Enterprise Edition |
Platform | 64-bit | 64-bit | 64-bit |
Operating System | Windows 2008/2012 Server or Windows 2008 R2/2012 R2 Server Standard Edition (fully patched) | Windows 2008/2012 Server or | Dedicated Windows Server 2008/2012 or 2008 R2/2012 R2 Standard Edition (fully patched)
|
Application Memory* | Minimum - 4 GB Recommended - 8 GB | Minimum - 8 GB Recommended - 16 GB | Minimum** - 16 GB Recommended - 32 GB |
Processors* | 4 Cores | Minimum - 4 Cores Recommended - 8 Cores | Minimum** - 8 Cores Recommended - 16 Cores |
SQL Server Edition | Microsoft SQL Server 2008/2008 R2/2012/2014 Standard Edition (fully patched) | Microsoft SQL Server 2008/2008 R2/2012/2014 Standard Edition (fully patched) | Microsoft SQL Server 2008/2008 R2/2012/2014 Enterprise Edition (fully patched) |
SQL Instance Memory | 4 GB | Minimum - 4 GB Recommended - 8 GB | Minimum 16 GB |
SQL Server Processors | 4 Cores | 8 Cores | Minimum** - 8 Cores Recommended - 16 Cores |
SQL Server Storage: |
|
|
|
| SQL System Disk (Mirrored) | 10 GB | 10 GB | 10 GB |
| SQL Page File Disk | 10 GB | 10 GB | 10 GB |
| SQL Database Disk | 20 GB per year | 60 GB per year A separate physical hard disk, formatted with 64K blocks, or RDM on storage LUNs | Maximum 600 GB per year A separate physical hard disk, formatted with 64K blocks, or RDM on storage LUNs |
| SQL Transaction Log Disk | 1 GB | 5 GB A separate physical hard disk, formatted with 64K blocks, or RDM on storage LUNs | 50 GB A separate physical hard disk, formatted with 64K blocks, or RDM on storage LUNs |
| SQL Temp Database Disk | 20% of Database Disk size | 20% of Database Disk size Recommended - A separate physical hard disk, preferably solid-state drive (SSD) | 20% of Database Disk size Recommended - A separate physical hard disk, preferably solid-state drive (SSD) |
| SQL Temp Database Log Disk | 1 GB | 5 GB | 5 GB |
| SQL RAID | RAID 10 or similar | RAID 10 or similar | RAID 10 or similar |
Additional Software & Services |
|
|
|
* This refers to hardware allocated for the CardioLog application pool and services, not for the CardioLog SQL server
** Up to 2,000,000 page views per month
*** The CardioLog application and database can be installed on-premise on physical servers or virtual machines, or hosted on Microsoft Azure virtual machines (which meet the above hardware and software requirements). When hosting CardioLog Analytics on Microsoft Azure virtual machines (IaaS) and tracking a SharePoint on-premise farm, a site-to-site VPN is required.
The amount of resources needed for the CardioLog Scheduling Service nightly processing depends on -
- Number of websites
- Website size
- Number of scheduled reports
- The timeframe for the reports (reports for 365 days demand more resources then reports for 30 days)
- The number of events (traffic) coming in from the portal at the time of report processing
Importing large websites that consist of millions of items, user information for hundreds of thousands users, and generating hundreds of daily reports will consume most of the CardioLog application server resources. The more resources allocated, the better.
Database Sizing
Hard disk allocation depends on the size of the monitored environment and the level of activity taking place in the portal. Additional factors that should be considered are backup and clean-up policies, and the amount of data accumulating over time. For example, an installation with 10 million usage events per month requires a total disk space of about 600 GB for a single year of data.
In practice, the estimated database size depends on the size of the CardioLog event tables. The following formula depicts the sizing calculation for the database:
Sd = Srd × Nu × (Ns + Nsr + (Ne × 2)) × P
Where:
Sd = estimated size of the database
Srd = average size of data per event (5 KB)
Nu = number of users in the monitored environment
Ns = average number of search operations per day per user (each search operation generates 1 event)
Nsr = average number of search results clicks per day per user (each search results click generates 1 event)
Ne = average number of non-search operations (views, duration) per day per user (each non-search operation generates 2 events by default)
P = length of the monitoring period - in days