Actually, we tried this criteria (where we used exactly same dummy characteristics as shown in your screenshot) on only single UserID which was reporting higher Parser Time. But it was not making use of the POW under SessionWDID for its parsing work.
So we thought to try the POW criteria on every user to see whether this new feature works on our box or not.
But still we faced the same issue (where no one user is SessionWDID is making use of POW).
I agree with your point not to use the Profile* for entire user community which may lead to bad consequences. But we did that just to isolate whether the POW criteria make the PE work to complete under designated workload or not.
As you suggest, we will try again with below by tweaking the EPT a little and keep you posted.
Classfcn Criteria:
USER: = * ACCTSTR: = * APPLIC: = * PROFIL: = * ALL_AMP: EPT >=10000000000000
Actually, we tried this criteria (where we used exactly same dummy characteristics as shown in your screenshot) on only single UserID which was reporting higher Parser Time. But it was not making use of the POW under SessionWDID for its parsing work.
So we thought to try the POW criteria on every user to see whether this new feature works on our box or not.
But still we faced the same issue (where no one user is SessionWDID is making use of POW).
I agree with your point not to use the Profile* for entire user community which may lead to bad consequences. But we did that just to isolate whether the POW criteria make the PE work to complete under designated workload or not.
As you suggest, we will try again with below by tweaking the EPT a little and keep you posted.
Classfcn Criteria:
USER: = * ACCTSTR: = * APPLIC: = * PROFIL: = * ALL_AMP:
EPT >=10000000000000