|
Post by emiliano on Aug 2, 2019 15:31:58 GMT 1
Hola queria consultar por un problema que me esta pasando con Vdos.. resulta que hago un proceso, (busca datos en un dbf y lo lista en la pantalla) lo cual tiene una demora de mas de 20min. hice la misma prueba en una pc con S.Operativo 32bits, donde no se usa el Vdoos y hace el mismo proceso en 7min. Alguna solucion? Desde ya muchas gracias.
|
|
|
Post by Jos on Aug 2, 2019 15:51:05 GMT 1
I suppose the database is located on a server since 20 versus 7 minutes isn’t actually that bad . Have a look at www.vdos.info/faqs.html - Miscellaneous - My application (sometimes) runs slower than before. It’s inherent to emulation. I also suppose the program is searching for non-indexed data, reading the whole file sequentially. Then the quickest way would be to run the program at the server (bypassing the relatively slow network). If the data is indexed, the index file would be real fragmented/unbalanced. Consider a onetime rebuild of the index file. Jos
|
|
|
Post by emiliano on Aug 2, 2019 18:07:04 GMT 1
Hola, mira te comento que hice la prubea en el servidor y sigue igual, demora mas de 20minutos. es mas probe el mismo proceso con otro sistema para virtualizar sistemas de 16bits y en este caso lo hizo en 4minutos. es decir que el problema esta en el Vdos.
|
|
|
Post by Jos on Aug 2, 2019 18:37:11 GMT 1
The text of the mentioned ends with: But w/o user interaction, few BIOS/DOS calls, little disk access, lengthy CPU intensive tasks. Like sorting database records in memory, the slowness of the emulated CPU will become more profound. You just have to life with that.
An emulated CPU is just slower than the real thing.
Jos
|
|
|
Post by emiliano on Aug 2, 2019 18:41:23 GMT 1
Entiendo lo que me decis, pero con otro programa emulador parecido al vDos, el proceso que te digo lo hace en 4minutos. Es decir que comparando ese mismo proceso con los dos emuladores, el vDos se ve que tiene algun problema y demora mucho en hacerlo, en cambio el otro lo hace en poco tiempo.
|
|
|
Post by Jos on Aug 2, 2019 18:58:15 GMT 1
That would be DOSBox (or a mod). In www.vdos.info/faqs.html - Miscellaneous - SHARE – Record locking (RL) by multi-user applications: …DOSBox (mods) caches disk operations,… …DOSBox file caching is also why it can sometimes outperform Windows NTVDM, and then certainly vDos. And if you would ask: No, vDos will never do file caching. That can only be done safely by the operation system managing the drive. Jos
|
|
|
Post by Jos on Aug 3, 2019 23:17:56 GMT 1
Well, more complains about vDos being slow(er). Something like this:
< vDos is 10 times slower than NTVDM! > Then vDos is no practical option. You can’t have for instance entering orders taking 10, instead of 1 minute. < No, it’s the one most time consuming task, to compare performances. 100 versus 10 minutes! > If a daily task, vDos is still no option. < That task should be executed at the end of every month, though actually twice a year.
If you consider/evaluate only one rarely used task of your program, vDos certainly is no option (to you). Jos
|
|