No Impact Factors

The following factors have no impact on Archer performance:

APIs

An Application Programming Interface (API) is a mechanism for loading data into Archer. Archer employs a few different APIs:

Web Services API

The Web Services API is ideal for operating on smaller hardware, and designed for transactional integrations with other systems. However, during a single bulk load, using a data feed is recommended for 30% increased performance speed.

RESTful API

The RESTful API call loads records 1 at a time, but loops these calls in such a way as to load very large quantities of data quickly. The RESTful API is called through any Archer Web Servers in a given deployment. It has a minimal effect on other users accessing the system at the same time, save for normal behavior around recalculations.

Content API

The Content API acts as a translation layer that converts Archer Metadata and Content into logical entities so that those entities can be consumed in the same way that they are by users in the Archer UI.

Inline editing

Inline editing enables users to make changes to data content directly from search pages. Inline editing can have a minor to moderate impact on Archer performance, depending upon how many fields underlying search pages return, and whether Expand All is enabled.

Trusted IPs

The Trusted IPs feature enables the Archer administrator to limit access to Archer to a specific list of known IP addresses.