Implement for scale

Use these guidelines as you test, and work with your Medallia expert to ensure your implementation is not so large as to cause performance issues.

Hierarchy size

Consider the size of your hierarchy, including the number of units and unit groups. Determine whether all of the units are truly needed, and delete non-essential units. For example, consider deleting units to which no survey responses will be associated. Contact your Medallia expert before deleting large numbers of units. For more information, see Organization management.

Note: Inactive units have the same performance impact as active units.

Large scale flags

An account is considered as a large scale account when any of these numbers are above the specified limits:

  • Units — 100,000.

  • Unit groups — 50,000.

  • Users — 50,000.

  • Records — 100,000,000 records received per year.

  • Historical record import — 10,000,000 records.

K-field and R-field optimization

Ensure that you have optimized your K-fields and R-fields, as described in K-field calculation optimization tips and R-fields.

Limit the number of dropdown fields (for unit groups and segments) on the Control panel to no more than five. If you need more, consider adding more fields in the segment dropdown. For more information, see Filters and control panels.

Report size and location

Consider the size of your reports, not just for the number of rows, but the total number of cells (rows multiplied by columns) displayed. This applies to all reports. For very large reports, assess the business case and consider whether an export would best serve the company.

If you have a common dashboard used by most users, large reports can degrade performance. Consider placing large reports on a dedicated subtab in navigation.

For more information, see Reporting.

Load times

Test to see whether any user-facing page taking more than a few seconds to load, or is otherwise noticeably slow, by refreshing the page 10 times in quick succession. If the page fails to load or results in an error, contact to your Medallia expert.

Processing

A Backfill can take multiple days or be disabled: you cannot plan a tight launch timeline around them.

Text Analytics processing (either topic processing or clustering) takes a considerable amount of time and should not be counted on to complete quickly.

Index creation (such as selecting Used for duplicate checking on an E-field) takes a long time, create those fields as far in advance as possible.