How can we help you today? How can we help you today?

GUI performance with 6.0

I am dissappointed 6.0 still wants to pull server data down to local cache. I just started playing with it an hour ago. And it is still trying to bring down server data to local cache. That's with only 2 instances registered in the GUI. Please seriously consider ditching the local cache concept, it's a real performance killer.
DonFerguson
0

Comments

3 comments

Sort by
  • DonFerguson
    Perhaps I jumped the gun a bit on my last posting. The poor performance was against a SQL Server instances with the SQL Backup 5.4 installed components using the 6.0 GUI, not the 6.0 backend components. I upgraded a DEV instance to the 6.0 backend components and the activity history came up almost instantly. A significant improvement as long as 6.0 components are installed on the backend.
    DonFerguson
    0
  • HJoyce
    Glad you saw an improvement, despite the false start.
    HJoyce
    0
  • DonFerguson
    Well I still don't like the concept of local cache, but at least the 6.0 GUI is more usable than the 5.4 version is. With lots of instances registered, the performance still leaves lots to be desired. I would recommend that all data be stored in the SQL Server instance database and that the client just queries data as needed. That's how it's supposed to work. The idea of pulling all the data down locally is not in allignment with the client server concept and causes a huge amount of unnecessary overhead.
    DonFerguson
    0

Add comment

Please sign in to leave a comment.