Program runs slowly, program "lags"

Program slowdown in the vast majority of cases occurs due to slow database response.

This can happen due to a large number of records in the database. Moving some orders to the archive does not affect performance, as the archive is also located within the database.

Archived orders reduce the speed of displaying orders in the list but still increase the overall response time from the order database.

Reasons why database response may slow down:

For local and network database:

  1. The database is overloaded and maintenance hasn't been performed for a long time.

Actions that can be taken:

  1. Create a new empty database. You can do this yourself, we will send instructions. Or our specialist can do it by connecting remotely. In this case, your old orders will not be in the clean database.

  2. Perform database maintenance. In this case, all your data will remain. For maintenance, contact your database administrator or our specialists.

  3. Perform database maintenance with deletion of orders for a certain period. If you maintain inventory and calculations, balances and debts may "shift".

  4. For local database - switch to a network database, which has significantly more resources.

Reasons for network database:

  1. Connection to the database via wireless connection is slow.

    WIFI speed is always lower than wired connection. Due to many reasons: distance from the router, number of wireless clients, etc.

    Actions that can be taken: connect all computers to the router with a cable.

  2. Poor quality network equipment.

    Cheap equipment can significantly affect query execution speed.

    Poor quality equipment can be considered: cheap routers: wifi dongles, routers provided by internet providers, cheap switches (hubs, switches).

    Actions that can be taken:

    Replace equipment with better quality. To support 10 workstations in an office, a router and a managed switch costing 4-5 thousand rubles each is sufficient (price is current as of mid-2023).

  3. Poor quality internet connection.

    If remote computers connect to the network database through the internet, the speed will be lower than when working within the local network.

    Wireless internet sources (4G modem) significantly negatively affect query execution speed.

    Actions that can be taken:

    1. Switch to better quality wired internet.

    2. Organize access via RDP (Remote Desktop).

    Important note: internet speed is not equal to query execution speed! If your provider claims a speed of 100 megabits, which is confirmed by speed tests, this does not mean that the response speed of an individual query will be high.

    You can check the response speed of an individual query using the "ping" command. If the response speed is more than 5 ms, this leads to "lagging" in EasyCeiling.

    Please note that slow database speed can significantly affect the program's performance.

    If a query executes slowly, the database may reject it. This can lead to important information not being written to the database, or conversely, not being deleted from it.

    In this case, errors may accumulate in inventory, cash register, and dealer debts.

    If you cannot independently determine the cause of slow operation, EasyCeiling specialists can perform diagnostics using remote connection.

What to do if the database is slow?

  1. Contact our specialists for diagnostics and maintenance of the database

  2. You can independently reduce the load on the database, but this helps only to some extent

How to work with the program — we will show you how to create orders, work with drawings, and print documents.

What questions does this article answer?

  • How to fix slow program performance in EasyCeiling?

  • What are the performance optimization features?

  • How to manage program speed?

  • What are the performance tools?

  • How to handle slow operation issues?

  • What are the optimization procedures?

  • How to ensure program efficiency?

  • What are the performance features?

  • How to troubleshoot speed issues?

  • What are the performance requirements?

  • How to optimize program workflow?

  • What are the speed options?

  • How to manage performance settings?

  • What are the optimization guidelines?

  • How to verify program speed?

  • What are the performance tools?

  • How to handle complex performance issues?

  • What are the speed standards?

  • How to ensure precise optimization?

  • What are the best practices for program performance?