Geo SCADA is Running Very Slow

[abdullah123456789]

Hello, 

I have Geo SCADA Expert 2021 and February 2022 Update version. Its version is 6.84.8108.1. It was bugging so it is running very slow since yesterday. When i analyzed the Task Manager, I've seen "Geo SCADA Expert Database Server" and "Geo SCADA Expert ODBC Driver" use too much memory on CPU as in the screenshot.

My RAM is 32 GB and computer is 64 bit.

I have enough space in disk.

[BevanWeiss]

That's not a very optimum disk arrangement.

A single disk for your OS, and your logs, and ALL of your historical data.

What type of disk is it, SSD or HDD, and how many IOPS is it rated for?

I suspect your RAM usage is due to GeoSCADA Expert not being able to stream data to the disk sufficiently fast, and hence it is ending up buffering lots in RAM.

You should look at the hardware recommendations in the installation documentation.

Once you're meeting the requirements, and if you still experience this issue, then you should escalate this with your local Schneider Tech Support office.

[geoffpatton]

What is using the ODBC driver? A SQL query that is run to frequently, a query of a large amount of data or a complex query can cause the database to have poor performance. If you are querying history and doing something like Min or Max on the data it is very inefficient. Look into using the Historic Views for stuff like that. You can also create custom historic views. Historic views are server configuration items and have to be set on each server independently, if you have redundant servers.

[abdullah123456789]

Hi,

I tried solutions in the above but it didn't work. Geo SCADA is still running very slow and sometimes stops working. I viewed the log files of database for solve this problem but i couldn't something. I'm sharing some example log files for your analyze.

[AdamWoodland]

The DBHIS flush logging in your logs suggests that whilst your disks aren't very fast (could be HDD, could be incorrect anti-malware solutions) it does appear to be keeping up with the amount of data going on, i.e. some flushes complete in 500mS rather than the full 1000mS.

Your lock usage is sitting around 80% that is probably the cause.

You need to contact support and work through the problem with them, they'll take you through additional logging and settings that would help diagnose the problem.

Smells like logic though, you seem to have a lot of logic programs triggering, but support can help you enable the logging to identify this.