General information
Category:
VFP Compiler for .NET
Hi Thomas:
You really know several tricks!. Our scanning with our TableLayer turns to be faster (for now I would not dare to say a lot faster) than VFP, but only in big tables, I'm doing benchmark comparisons with a table with 800 million records and 926 bytes by records.
Because this table has nearly 800 MB, in my test machine with 1 GB ram, VFP has a hard time caching the table and arrives later than our TableLayer.
With easily cached tables (few MB with in relation to the memory available), because VFP does extensively caching, it beat us, for now... Just wait we also enable this Caching Tricks in our TableLayer and the thing will get better.
>Hi Markus,
>
>when closing Table1 you delete the index file afterwards.
>Usually it is faster to delete the tag before closing, as VFP keeps the index file buffered and flushes on closing to disk - a step definitely not needed if you delete the index file afterwards. So save another few ms by deleting the index tag and closing the table.
>
>regards
>
>thomas
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only