Slow response - what kind of logging should I enable?
Hi,
We using RDM also from our India location connecting via VPN to a database located in our (Dutch) data center.
I have just seen a session (shared to show me the response) when selecting a session to be edited (right click and choosing Edit Entry) it takes upto a minute to get the edit window to pop up.
What kind of logging should I have the user enable so I can forward the logging result to you so you can have a look what is causing this slow response?
Regards,
Jan-Pieter
All Comments (5)
You can open the profiler in Help-> Profiler
David Hervieux
Do we need to increase the debug level? Or do you want to start with the basic (0) level?
With the profiler 0 will be ok
David Hervieux
This is for an edit entry action:
LoadConnectionList...
LoadConnectionList : 22 ms
LoadConnections [Microsoft SQL Server/SQL Azure : xxxxx]...
Connection cache up to date
DecryptData : 1 ms - Count : 703
DeserializeData : 334 ms - Count : 703
LoadConnections [Microsoft SQL Server/SQL Azure : xxxxx] : 65047 ms
FrmConnection.LoadGroups...
FrmConnection.LoadGroups : 78 ms
LoadConnectionList...
LoadConnectionList : 0 ms
LoadConnections [Microsoft SQL Server/SQL Azure : xxxxx]...
Connection cache up to date
DecryptData : 1 ms - Count : 703
DeserializeData : 344 ms - Count : 703
LoadConnections [Microsoft SQL Server/SQL Azure : xxxxx] : 79474 ms
Jan-Pieter,
There are few things to look at.
First, we see that the LoadConnections (aka read the data from the database) is taking 65-80 seconds. Most likely due to network speed and latency. In contrast, since you have about 700 sessions, read from a local network SQL should take less then 1.5 seconds.
You have a few options:
1 - use intelligent caching, the first load would be just as slow, but every other refresh(edit) will be faster (less data to transfer)
2 - you could uncheck (File -> Options -> Advanced -> Force refresh before edit entry) Keep in mind this could cause users to edit "old" copies of entries.
3 - enable Offline Read/Write and work offline most of that day and sync the changes every few hours or at the end of the day
You could actually do all three or any combination that you like to alleviate the network latency.
Regards,
Stéfane Lavergne