D
dbeavon
Guest
Not sure what Linux has to do with anything. We had recent call with the OpenEdge product group, and they assured us that there were no technical reasons why their products should perform substantially different in Linux vs Windows. Aside from system calls, the machine code is the same, and runs on the same chips. Vendors that sell disk are equally happy making money from both OS'es. I've been very happy using OE products on Windows, especially after coming from HP-UX, which is a pretty outdated platform. If you have disk i/o problems, they should affect other applications too. You can isolate disk i/o problems first, before assuming the fault is with Progress. I'd highly recommend a disk benchmarking tool like "sqlio" (don't be scared by the name, it is independent of SQL server). You can download it from here: Download SQLIO Disk Subsystem Benchmark Tool from Official Microsoft Download Center Here are some basic instructions to getting started. The SQL Server Sqlio Utility - Simple Talk You can compare your sqlio results between a system that performs poorly and one with acceptable I/O performance. The tool will allow you to measure both random and sequential I/O. And it will allow you to specify the number of outstanding/concurrent I/O operations. It will also let you specify your choice of block size. 30 seconds sounds like a very long time for this. Since you are using Windows, couldn't you simply open Resource Monitor and see if there is a disk issue from there? I'd suggest looking at the total throughput in bytes/sec and also at the response times (circled). An SSD's response time should stay very low (<3 ms) for most single-user activities. Note that you can see virus scanning activity from here too (eg MsMpEng). If you don't see anything of interest on the Disk side of things then flip over to the CPU tab and see if you are capped on a CPU core. Remember that you can be maxed out on CPU *before* you reach 100%. For example if you have four logical cores and have a synchronous workload, you may only see CPU reach the 25% mark but this still implies that your process is in fact CPU-bound. It is quite common for Progress database operations to be CPU-bound, as frustrating and counter-intuitive as it may seem. And when they do become CPU-bound, often times the operations neglect to use more than one of your logical cores at a time.
Continue reading...
Continue reading...