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 2003/2008/2012 Server or Windows 2003 R2/2008 R2/2012 R2 Server Standard Edition (fully patched) | Windows 2003/2008/2012 Server or | Dedicated Windows Server: 2003/2008/2012 or 2003 R2/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* | 1xQUAD | 2xQUAD | Minimum** - 2xQUAD Recommended - 4xQUAD |
SQL Server Edition | Microsoft SQL Server 2005 SP 4/2008/2008 R2/2012/2014 Standard Edition (fully patched) | Microsoft SQL Server 2005 SP 4/2008/2008 R2/2012/2014 Standard Edition (fully patched) | Microsoft SQL Server 2005 SP 4/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 | 1xQUAD | 2xQUAD | Minimum** - 2xQUAD Recommended - 4xQUAD |
SQL Server Storage System Disk (Mirrored) Page File Disk Database Disk
Temp Database Disk
Temp Database Log Disk RAID |
10 GB 10 GB 20 GB per year
1 GB
20% of Database Disk size
1 GB RAID 10 or similar |
10 GB 10 GB 60 GB per year 5 GB 20% of Database Disk size 5 GB RAID 10 or similar |
10 GB 10 GB Maximum 600 GB per year 50 GB 20% of Database Disk size 5 GB 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)
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