The 20 transactions max in the controller response time graph view and N/A in numeric column view is unacceptable! Need to be able to have insight on all transaction performance!

All,

This must be changed again.   back in effect starting somewhere in a patch beyond LR2022R2 and also in LR2023R1.   This is a unacceptable mindset to limit this being shown not only in the colored graph view but, also the actual reponse time in the column view.  If resources are the concern here, require more horsepower for others using lesser devices, not for folks running servers and more that sufficient resources on their machines.  

The problem/risk is the test operator cannot SEE ALL the response times for ALL THE transactions at once.  The risk is not seeing a transaction that is have issues in either the graph or in the actual numeric output within the columns... the N/A is not an acceptable measurement or any mean as an indicator that the transaction is operating normal or having an issue.  The test operator is BLIND to the performance of ALL transactions at once.  Which ENTIRE DEFEATS THE PURPOSE of a performance test.  By not even showing ALL transactions in the graph where spikes or stalls or other visual indicators would normally give a heads up to go look at the actual response times in the list, there is no value in the graph (or list view).

SHOW THEM ALL or find another solution.  Limiting this view to 20 is useless to test operators with more than 20 transactions in a test.

This was an issue way back, then it was resolved for years ... now its back!