Hi everyone,
I've been using JTL-Wawi for our inventory management for quite some time, but I've recently hit a persistent technical issue where the interface becomes sluggish and our worker synchronization starts to time out.
I am currently using a safe free community setup to handle some automated data logging and local script execution on the same workstation I use for my Wawi operations. I've noticed that whenever the background executor starts a heavy processing cycle, JTL-Wawi starts throwing "SQL Server Connection" errors, and the product search feature becomes incredibly slow. It feels like the background process is competing for the same high-priority CPU threads and disk I/O that the SQL database needs for real-time inventory updates.
I have a few related technical questions for the shop owners and sysadmins here:
I'm not sure if the way a safe free style environment manages its internal threading is causing a resource contention issue with the .NET framework or the local SQL Express instance. Has anyone else encountered performance bottlenecks or "Socket Timeout" errors in their worker logs while running high-level script executors in the background? I am also wondering if there is a specific way to isolate the executor's CPU priority so it doesn't starve the JTL processes, or if I should consider moving the database to a dedicated server.
I really need to keep this automation active while I manage my orders, but the constant UI lag is making it hard to process shipments. If anyone has experience optimizing a Windows environment for concurrent usage of heavy script executors and JTL software, I'd love to hear your advice!
Thanks for the help!
I've been using JTL-Wawi for our inventory management for quite some time, but I've recently hit a persistent technical issue where the interface becomes sluggish and our worker synchronization starts to time out.
I am currently using a safe free community setup to handle some automated data logging and local script execution on the same workstation I use for my Wawi operations. I've noticed that whenever the background executor starts a heavy processing cycle, JTL-Wawi starts throwing "SQL Server Connection" errors, and the product search feature becomes incredibly slow. It feels like the background process is competing for the same high-priority CPU threads and disk I/O that the SQL database needs for real-time inventory updates.
I have a few related technical questions for the shop owners and sysadmins here:
I'm not sure if the way a safe free style environment manages its internal threading is causing a resource contention issue with the .NET framework or the local SQL Express instance. Has anyone else encountered performance bottlenecks or "Socket Timeout" errors in their worker logs while running high-level script executors in the background? I am also wondering if there is a specific way to isolate the executor's CPU priority so it doesn't starve the JTL processes, or if I should consider moving the database to a dedicated server.
I really need to keep this automation active while I manage my orders, but the constant UI lag is making it hard to process shipments. If anyone has experience optimizing a Windows environment for concurrent usage of heavy script executors and JTL software, I'd love to hear your advice!
Thanks for the help!