Lookout 6.0 and Citadel 5 Slow to Connect and Display Data

[skibum019]

Wondering if anyone else is seeing this.

We had a Lookout 5.1 Citadel 4 database running about 75-100 data points. We use hypertrends for viewing the trended data. In the old version, the hypertrends and historical data would be presented on the screen nearly instantaneously. We recently upgraded to Lookout 6.0 and Citadel 5. The hypertrends now take minutes to display and often times come in choppy. This is VERY inconvenient, especially when we try to connect other clients over our T1 WAN connection.....display time is VERY long.

I don't want to update our other Lookout system to 6.0 until this issue is resolved, our other system has a database that has somewhere in the realm of 3000+ data points it is tracking, and we can't afford to lose the speed for the trending displays.

Thanks for any input in advance.

[Danny G.]

Hello,

Lookout 6.0 uses Citadel 5. Citadel 5 is very robust and has been optimized to avoid corruption of databases. Much more error checking has been implemented in Citadel 5 in order to make it more robust. For this reason Citadel 5 does take more time to access.

Regards,

Danny G.
Applications Engineer
National Instruments

[nickf]

skibum019,

Have you tried using the ActiveX NI Hypertrend to view traces in Lookout? This is the same ActiveX object used by the Historical Data Viewer in MAX and should give you enhanced performance.

Nick F
National Instruments

[seoul04]

I complained to ni about the fact that nicitdl5 is using a lot of processor resources on the computer running the server process. As an answer I received the same bla bla ... more robust ... bla bla. The thing is that it is happening only when the client is accessing the server from the network. When they are on the same computer every thing is fine. I think it is more of a communication problem. You can use the performance monitor to graph the network activity of nicitdl5 to see that it is receiving a lot of packets while sending almost nothing. That leads me to the hypothesis that the client is making a lot of useless request (buggy hyper.cbx?) to the citadel server.

Still, I'm reassured to see that I'm not alone facing that performance issue but I think that we'll have to wait for 6.1!

[skibum019]

Yes, I too think there is something buggy about it. I tried the NI ActiveX Trend, which is a very nice component, but it too had/has the same problems with poor response times if any at all. This is very disappointing from my standpoint, one of the primary original selling points for me on Lookout back in the 4.0 days was its functionality in a client/server mode, with the existing situation with 6.0 that is totally negated by the fact that it does not function well and causes the end users more frustration then assistance.