Hello -
It seems that the devart driver is significantly slower to load a result set than the Microsoft Visual Foxpro Driver.
It seems this way with either the 32 or 64bit drivers.
Ive determined that the RecordSet.MoveNext() method is where the bottleneck is. Is there any workaround for this, or has anyone else experienced this?
In my tests the 32bit Microsoft driver loads the results, and is able to parse the recordset almost immediately, while the devart driver takes significantly longer.
Any ideas?
[EDIT]
This is mostly an issue on a MS Server 2019 running as a Terminal Server (Remote Desktop Session host).
Visual Foxpro - Slow Recordset Parse
Re: Visual Foxpro - Slow Recordset Parse
Hi there,
Thanks for your information but in order to investigate low performance of our driver please send us all table files (*.DBF, *.CDX, *.FPT, etc.) where the issue occurs.
You can send them using the contact form at our site:
https://www.devart.com/company/contactform.html
Regards
Sergey
Thanks for your information but in order to investigate low performance of our driver please send us all table files (*.DBF, *.CDX, *.FPT, etc.) where the issue occurs.
You can send them using the contact form at our site:
https://www.devart.com/company/contactform.html
Regards
Sergey