Answer by James K. ·
See if this helps:
HTH
James
Answer by mark e. ·
With regards to James' comment on Software Private Agent (SPA), think of this like an on-premise Backbone node. It uses the same scheduling and alerting logic as Backbone, but is installed (by you) on your on-premise hardware. Unlike PLM, SPA can run multiple browser engines concurrently and can scale to 1000s measurements per hour - PLM is a single process application so can only run as many tests that logically fit into a 60 minute block. Because SPA uses the backbone scheduling engine, test execution is almost instant - no waiting for populations to. It also means that scheduling is much more precise, stating tests per minute opposed to #tests per hour.
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 12, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 12, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 12, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 12, 4:00 pm CET / 10:00 am ET
Register here
Increasing scheduled test frequency 2 Answers
Data from 34 days ago 1 Answer
PLM server requirements 2 Answers