Slow query on Event tables
Performance degrades when querying MKT_EVENT_P711 and MKT_EVENT_P713 from the DF_Wait dataflow.
When the Outbound campaign's (PR-xxx) dataflow is running and a DF_Wait dataflow starts, the dataflow nodes consume 100% CPU and the outbound Program Run (PR) performance degrades. Additionally, the DF_wait dataflow takes more than 20 minutes to process the records (1 to 10).
Steps to Reproduce
Run an event Campaign.
A defect in Pegasystems’ code or rules.
The DF_Wait dataflow generates queries with the Where clause on CustomerID because the Event dataset (for the campaign output table) is keyed on the CustomerID property. However, there are no indexes on the CustomerID column when the EVENT table is created.