Information générale
Catégorie:
VFP Compiler for .NET
Hi Samuel,
>You are right, but you are a very knowledgeable man, and the tricks you could do are not in the general domain. For example using a ram disk for tmpfiles could speed a lot cursor operations in VFP. How many of us are using that "old playbook" trick?.
I do a variation of that <g>: For large tables often searched for particular fields I create separate index files and put them on a ram disk, and sometimes the tables as well. If they are mostly read, compressing helps to put more onto the RAM disk. Also using different spindles gives you a similar boost as using a RAMdrive. So plan for the version *after* the release a possibility to define/switch cursor location and/or tmpfile path (MS aknowledged that reguest as useful but will not implement it). JBOD used intelligently often reduces time needed by a third.
I have thought about searching for additional disks or creating a ram disk automatically if the machine is beefy enough in the setup, saving that info to a dbf read at startup to run under the best configuration for that particular machine. But might be overkill for a simple contest...
>So don't worry, we also want to get this thing out ASAP. I hope later you can send me some tricks about the debuting version ;-)
Sure enough ;-)
regards
thomas
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement