Start time (maybe end time)

Posts   
 
    
Puser
User
Posts: 220
Joined: 20-Sep-2012
# Posted on: 05-Oct-2019 14:17:24   

Using ORM profiler v2.0.1

I'd would like to see a start time (and maybe end time) for the connection so I can see which connections overlap on the same time (to understand performance issues and locking issues for example) Maybe this is also possible on the other activity rows, while you're at it...?

daelmo avatar
daelmo
Support Team
Posts: 8213
Joined: 28-Nov-2005
# Posted on: 07-Oct-2019 08:08:27   

Hi Puser,

You can see the start time of the query (executed on) in the "General Statistics" sub-tab of the query.

To see the time the connection was opened/closed you can use the "Low-level activity overview" tab... (ref)

Is that enough for your needs? If not, please elaborate more to clarify how you would want it, so the team can evaluate it as a feature request.

David Elizondo | LLBLGen Support Team
Puser
User
Posts: 220
Joined: 20-Sep-2012
# Posted on: 07-Oct-2019 08:55:05   

thank you, I would have hoped this could be a column I could choose in the realtime viewer (default maybe invisible) because the general statisics tab gives no overview (of course) and other wise i have to record always to snapshots and stop to see the results. that 's not my use case. I try things in realtime. can this be made possible please? or maybe you could also create some copy function from the readl-time viewer to a snapshot when needed (by button) to see the detailed information as in a snapshot?

Otis avatar
Otis
LLBLGen Pro Team
Posts: 38516
Joined: 17-Aug-2003
# Posted on: 07-Oct-2019 09:53:12   

Could you elaborate why it's not possible to start a recording, then run the tests, and then see the data in the low-level overview of the snapshot recorded?

the connection isn't locking anything, the query is. Performance issues also stem from queries locking/doing things, not from connections.

You can start a recording in the realtime tab, record activity, and then look at it and do further analysis. the real time overview doesn't have that info, as it's goal is to give an overview of what's going on at this time, e.g. you run a test / click a button and you see what activity results from that.

Grouping things for the low-level activity requires a period of time and all the activity in that period is then grouped. In real time that wouldn't be possible as the current time hasn't ended so a grouping would be costly.

Recording the snapshot will give you the insight you want. So I suggest you use that feature as it's meant for this situation simple_smile

Frans Bouma | Lead developer LLBLGen Pro
Puser
User
Posts: 220
Joined: 20-Sep-2012
# Posted on: 07-Oct-2019 10:29:48   

It's just nice to work in real-time in one window without starting/stopping things. It's always possible to do more actions by hand of course by starting/stopping, but when I can avoid it, I will. Mainly because I use this chronological connections view (my main view) A LOT. I have it on almost always. Then when I notice something, not really db testing, but other stuff, then I can resort to ORM Profiler. My application has different observers waiting with different 'time scales', so sometimes a change can trigger many other things/changes, where I have to watch that some timers don't get started too soon or too late (from a DB perspective). Then it is nice to see the starting time (only that) in the main view of ORM Profiler. but oke, if that is difficult, leave it then maybe you could add an option to 'auto record to snapshot'. like here

SD.Tools.OrmProfiler.Interceptor.InterceptorCore.Initialize("xxxxx",....);

or in ORM Profiler itself. when there is no tab open, it opens and starts to record.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 38516
Joined: 17-Aug-2003
# Posted on: 07-Oct-2019 13:34:20   

I understand simple_smile Perhaps we'll add it some day, but for now, I'd revert to the snapshot recording and use that. simple_smile

Frans Bouma | Lead developer LLBLGen Pro
Puser
User
Posts: 220
Joined: 20-Sep-2012
# Posted on: 07-Oct-2019 13:49:58   

ok. keep up the good work.