CubeView Reports Block Each other on Low CPU

dbeavon
Contributor

SOURCE: OneStream Champions

I have a cubeview in onestream. If I launch one of them via the api it runs in 45 seconds. If I start two of them at the same time, they both finish in about 1:20 (a little over a minute, which is almost double the 45 seconds).

 

 

image

image.png2140×180 24.7 KB

 

What is the reason for the extra amount of time that is spent per report when two are running concurrently? IE. what internal resource is being protected against concurrency? From a technical standpoint, it seems very unexpected that two readers would block each other in this way.

You can see in the screenshot that there is plenty of CPU available.

I’m assuming this topic isn’t specific to our environment or to this cubeview. Nothing we are doing seems exceptional or unusual in any way.

1 REPLY 1

scottr
New Contributor III

have you tried monitoring the database server metrics while running 1 report vs 2 concurrent reports?