Planning Analytics

Hi,

I do have a support ticket open for this (TS017250981) but since it relates to the demise of the rich tier and more generally to Perspectives itself I thought I would raise it here as well.

Our PAoC customer is reporting massive increases in Transaction log query times, to the point that the functionality is not usable.

In Perspectives using the rich tier the response time was 7 seconds, in PAW the response time was 43 minutes.  The query should have been searching over 35 files totalling 600MB.  This is 7 days of files, with a Save Data chore running at a high frequency.

Is this a known issue with the current implementation as this performance isn't acceptable for such a small query volume.

In addition, the query when run from PAW was found to be locking, i.e. TI processes were queueing behind it. 

I can't see a reason for this to be a locking activity, is this by design?

Cheers!

HI Steve,

I can attest to the very slow response times when query the transaction log.

I was trying to show something recently to a client and gave up after 5 awkward minutes and resorted to FindStr.

My log file was not huge and I only had the one as this was a non-production environment.

It was not always this poor but think something recently changed.

Hi,

I do have a support ticket open for this (TS017250981) but since it relates to the demise of the rich tier and more generally to Perspectives itself I thought I would raise it here as well.

Our PAoC customer is reporting massive increases in Transaction log query times, to the point that the functionality is not usable.

In Perspectives using the rich tier the response time was 7 seconds, in PAW the response time was 43 minutes.  The query should have been searching over 35 files totalling 600MB.  This is 7 days of files, with a Save Data chore running at a high frequency.

Is this a known issue with the current implementation as this performance isn't acceptable for such a small query volume.

In addition, the query when run from PAW was found to be locking, i.e. TI processes were queueing behind it. 

I can't see a reason for this to be a locking activity, is this by design?

Cheers!

Hi,

I do have a support ticket open for this (TS017250981) but since it relates to the demise of the rich tier and more generally to Perspectives itself I thought I would raise it here as well.

Our PAoC customer is reporting massive increases in Transaction log query times, to the point that the functionality is not usable.

In Perspectives using the rich tier the response time was 7 seconds, in PAW the response time was 43 minutes.  The query should have been searching over 35 files totalling 600MB.  This is 7 days of files, with a Save Data chore running at a high frequency.

Is this a known issue with the current implementation as this performance isn't acceptable for such a small query volume.

In addition, the query when run from PAW was found to be locking, i.e. TI processes were queueing behind it. 

I can't see a reason for this to be a locking activity, is this by design?

Cheers!

Hi,

I do have a support ticket open for this (TS017250981) but since it relates to the demise of the rich tier and more generally to Perspectives itself I thought I would raise it here as well.

Our PAoC customer is reporting massive increases in Transaction log query times, to the point that the functionality is not usable.

In Perspectives using the rich tier the response time was 7 seconds, in PAW the response time was 43 minutes.  The query should have been searching over 35 files totalling 600MB.  This is 7 days of files, with a Save Data chore running at a high frequency.

Is this a known issue with the current implementation as this performance isn't acceptable for such a small query volume.

In addition, the query when run from PAW was found to be locking, i.e. TI processes were queueing behind it. 

I can't see a reason for this to be a locking activity, is this by design?

Cheers!

Just to close this out, this is a known issue already being tracked on an APAR, PH61508.

Hi,

I do have a support ticket open for this (TS017250981) but since it relates to the demise of the rich tier and more generally to Perspectives itself I thought I would raise it here as well.

Our PAoC customer is reporting massive increases in Transaction log query times, to the point that the functionality is not usable.

In Perspectives using the rich tier the response time was 7 seconds, in PAW the response time was 43 minutes.  The query should have been searching over 35 files totalling 600MB.  This is 7 days of files, with a Save Data chore running at a high frequency.

Is this a known issue with the current implementation as this performance isn't acceptable for such a small query volume.

In addition, the query when run from PAW was found to be locking, i.e. TI processes were queueing behind it. 

I can't see a reason for this to be a locking activity, is this by design?

Cheers!

We are making some improvements to performance of the transaction log query over REST API.  These changes will be delivered in the next update to TM1 Server.  This will probably be the Planning Analytics 2.0.9.21 release and a corresponding 2.1.x release.

At the same time we are working on some major improvements to the PAW modeling workbench user interface for transactions logs.  We are introducing lazy loading, so as the modeler scrolls more transaction records from the query will be loaded.  This will allow the modeler to examine more than 1500 transaction records at a time.  There are a few other minor user interface improvements planned as well (e.g searching transactions from multiple users at a time).  These improvements will be delivered in a PAW update before the end of this year.

Just to close this out, this is a known issue already being tracked on an APAR, PH61508.

Hi,

I do have a support ticket open for this (TS017250981) but since it relates to the demise of the rich tier and more generally to Perspectives itself I thought I would raise it here as well.

Our PAoC customer is reporting massive increases in Transaction log query times, to the point that the functionality is not usable.

In Perspectives using the rich tier the response time was 7 seconds, in PAW the response time was 43 minutes.  The query should have been searching over 35 files totalling 600MB.  This is 7 days of files, with a Save Data chore running at a high frequency.

Is this a known issue with the current implementation as this performance isn't acceptable for such a small query volume.

In addition, the query when run from PAW was found to be locking, i.e. TI processes were queueing behind it. 

I can't see a reason for this to be a locking activity, is this by design?

Cheers!