Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

* The System Requirements apply to daily operations of CardioLog Analytics and do not include any custom actions, such as running product upgrades, executing scripts, importing IIS logs, etc. These type of actions may require additional resources.

...

The amount of resources needed for the and the time it takes for the CardioLog Scheduling Service nightly processing depends  jobs to complete depend on -

  • Number of content items (websitesWebsite , lists, list items, documents etc.)
  • Content size
  • Number of events (traffic) 
  • Number of scheduled reports
  • The timeframe for the reports (yearly 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 processingwidgets per report

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 import process for large environments may take a few hours up to a few weeks, depending on the import method (direct database access vs. API calls), import mode (full vs. changes only) and the environment size.

The more resources allocated, the better. 

 

Anchor
database sizing
database sizing
Database Sizing

...