Lookout 6 Slow Response

[Mike@DTSI]

We are currently moving our clients to Lookout 6, but have noticed some major issues.

When the server and client processes are opened on the dev. machine, displays are very unresponsive. Clicks to pots, buttons, etc. and delayed about 1-3 seconds. HyperTrends are shoppy, and take minutes to load (only 9 data points!). Client machines on the network are even worse, taking upwards of 10 minutes to load 1 hour of logged data (.1 resolution, very little fluctuation over 1 hour). Moving a panel via the titlebar causes the machine to slow, windows needing to be redrawn constantly.

The new SQL/MSDE server for Citadel also causes 90% processor usage with the process idle!

This appears to be a known problem, any ideas?
Mike

Dev. Machine Specs:
Windows XP Pro
Athlon 1Ghz, 512MB, 2x60GB RAID, ATI 9600 Video. (Not really that slow!)

[Mike@DTSI]

No information available? We will not be upgrading any of our clients to the new software until this is resolved, Lookout 5.1 runs great.

[Jeff M]

Mike,

Since this is a major upgrade to both the application software (Lookout 6) as well as the database (Citadel 5), performance issues can arise if something in the upgrade process is not completed as expected. We are doing are best to document all such issues that can arise for different upgrade scenarios. For example, if the Citadel 4 database was not converted properly to Citadel 5, issues may arise.

The only "quickfix" I can suggest is to try using the ActiveX NI Hypertrend to view traces in Lookout, as opposed to the regular hypertrend. This is the same ActiveX object used by the Historical Data Viewer in MAX and should give you enhanced performance.

You pointed out that Lookout 5.1 is working perfectly, so I would recommend judging whether or not it's worth the upgrade by viewing the new features that have been added to Lookout 6:
http://volt.ni.com/niwc/lookout/whatsnew.jsp?node=12511

If and when you decide to upgrade, myself or another Applications Engineer would be happy to walk through this process with you over the phone, to better understand the scope of your application and make sure we cover all our bases. Generally speaking there should not be this degradation in performance that you have described. As always, feel free to request support from us at:

ni.com/support

Regards,

Jeff M.

Applications Engineering
National Instruments

[Mike@DTSI]

The database is not converted, it is with a completely fresh starting point.

The reason we update software is to keep a more uniform code base available, making a change for one version instead of 3, etc.

The NI HyperTrend ActiveX also exhibits the same behavior.

To recreate the problem, simply start a new process and open the Task Manager. SQL server runs over 80%. No data is being logged or accessed by the process (Atleast from the developer items, what you guys do in the background...)

And to add a control subject: We have a live machine with roughly 35 logged points, Athlon 2600+, XP Pro, 1GB DDR, etc. does the same things!

Message Edited by Mike@DTSI on 05-10-2005 02:01 PM

[skibum019]

Mike,
Lookout 6.0 is buggy, and irregardless of what I have talked and tested with NI, I have the same problems. We have a dual processor machine running over 1GB of memory. I initially upgraded to 6.0 from 5.1 and had major problems. I Lookout all together from the machine and installed a fresh instance and started a new database per NI's recommendations (not too happy about limiting the access to old data.....) and started building a new system. Everything on the system itself seems to work fine, but clients have a horrible time connecting to data. Some can but are extremely slow, others can't open trends period. I was really excited about the NI ActiveX hypertrend functionality in 6.0, but with all the problems, we will likely have to revert back to 5.1 as well. The trends can take anywhere from 1 minute to update up to 15+ minutes to update, and then it is patchy even at that point. I think NI may have dropped the ball on the development of this one.

[JedRetherford]

Mike@DTSI and skibum09,

I am sorry to hear that you are having difficulties with Lookout 6.0. My co-workers and I in no way discount your concerns or doubt their validity. It seems quite obvious to me that both of you are having difficult issues.

That being said, I want to assure you that getting very good performance from Lookout 6.0 in the types of applications that you are describing is completely possible. I have talked to dozens of people who are doing just that. We have not seen the issues that you are describing in any of our applications here at National Instruments. In my opinion, this most likely points at a difference in style of programming, hardware, peripheral software, or networks.

That leaves a lot open for investigation. If you would both be willing, I would appreciate it if you could post, 1, a general description of your application, 2, details of the computer(s) having the trouble (HW, OS, and OS ServPack), 3, any peripheral software that is running on the machines (virus scans, firewalls, software updaters, thin clients, etc.), and 4, the details of the networking setup being used.

I am hopeful that with this information that we may be able to identify some similarities between the machines that you are having trouble with. In addition, if either of you can create a small, hardware-free, application that can duplicate the problems that you are seeing and post it, I would be willing to try running it to see if it is possible for me to duplicate your trouble. I am hopeful that others in this forum might also be willing to do the same.

So lets track down the problem that you are seeing and get it resolved. I look forward to your responses.

Regards,
Jed R.
Applications Engineer
National Instruments

[Mike@DTSI]

Dev machine 1:
Windows XP Pro
Athlon 1Ghz
512MB PC133
2x60GB Maxtor (Mirror RAID)
ATI 9600
Avast! Antivirus
No firewall

Dev Machine 2 (Laptop):
Windows XP Pro (SP1)
Athlon 1700+
512MB PC2700
1x20GB IBM
ATI IGP (7500)
Avast! Antivirus
No firewall

Test Client:
Windows XP Home (SP1)
Athlon 2200+
384MB PC2700
1x60GB Maxtor
SIS Integrated
Norton Antivirus
No Firewall

Live Machine:
Windows XP Pro (SP2)
Athlon 2600+
1GB PC2700
nVidia Integrated
Norton Antivirus
No firewall


All machines provide the same symptoms.

Application: Thats easy, just make a new process and watch the mouse jump. Have tried the ActiveX control, same problems. Have used exisitng processes, same problems.

My hypothesis: There is a redundant call(s) being made to the Citadel (SQL) Server. When Lookout first start the sqlserver.exe will idle at 0% CPU, when a new process is started (No additional objects), usage goes to 80-95%.

[Mike@DTSI]

Any ideas yet, i mean ill stick with 5.0 if you dont want our money...

[Jeff M]

Hi Mike,

Thanks for the detailed system specs. This is very valuable information for Lookout R&D team. Before you make your upgrade decision, please give me a call so we can try some things over the phone, as I want to make sure we cover all our bases. Please goto ni.com/support and open a new service request. I would be more than happy to discuss this with you in person.

Best Regards,

Jeff M.

Applications Engineering
National Instruments

[Mike@DTSI]

Im getting a thing saying "Your 30-day trial has expired..." haha, good idea 😉 I would actually like to have the information detailed here as to help other members/users of this forum/software. I am more than willing to test beta products also.
Thanks

Mike C.
Developer
Digital Telemetry Systems, Inc.
http://www.dtsicorp.com