D
dbeavon
Guest
>> was your temp-table memory-resident? Or did that involve DBI I/O? I suspect it was NOT memory-resident but I didn't get that deep in my investigation. Are there VST's for that? Or do I have to enable ABL tracing? Or maybe I just need to watch for file i/o in my temp directory? If I had to guess, it was probably using I/O on disk (local SSD) considering the number of records. But I've never seen the local SSD become a bottleneck for an ABL database applications. Usually the bottlenecks in an ABL client-session are related to waiting on round-trips from the database, or using a single CPU core.
Continue reading...
Continue reading...