MSX Basic Tokenizer. Should I?

Page 4/4
1 | 2 | 3 |

By farique

Rookie (23)

farique's picture

13-08-2019, 18:13

I remade the script without the savestates and it is now working like a charm!
It boots using the default machine or a specified one. An extension can also be specified in case the machine does not have a disk drive.

Using a Phillips NMS 8250 and a Sharp HB-8000 with a Microsol disk extension I had no problems at all. A stress test with a Terminal script to batch convert lots of files at once worked flawlessly. Even when the folder got full it just stopped saving the new files, no corruption.
I feared that opening several instances of openMSX at the same time and mounting the same folder as disk wold cause problems but or the timing of mounting didn't quite clash or they didn't care.

About the speed, I think the bottleneck now is just the time it takes to launch openMSX itself (~2-3s) but have yet to confirm.
The times I got using the TIME command on the Terminal where:
(didn't test with mute)

20 files .bas  to .asc ~95k total:
real 0m56.690s, user 0m0.878s, sys 0m1.221s

20 files .asc to .bas ~115k total:
real 0m55.474s, user 0m0.871s, sys 0m1.238s

Unfortunately I still don't know what was really causing the problem with the previous method, I changed several things at the same time and now I don't know which one was to blame. I know the basic files I was using (from MSX Archive) were mostly corrupted and I am ALMOST sure I had problems with the Sony 500P even using it normally.
I still want to do some stability (and better speed) tests and will report here.

By Manuel

Ascended (15763)

Manuel's picture

13-08-2019, 21:29

2-3 seconds? Strange...

On my 2008 PC I did this test:

$ time openmsx -machine Boosted_MSX2_EN -diska /tmp/bla /tmp/quit.tcl 

real	0m0,780s
user	0m0,170s
sys	0m0,166s

and quit.tcl contains:
after realtime 0 exit

So this measures the start-up time for a very large machine and using dir-as-disk. Less than 1 second....

If you can reproduce this, it must be something else.

By farique

Rookie (23)

farique's picture

21-08-2019, 23:40

Ok, so I did the same test as you (I don't have the files for a Boosted MSX2 so I used the plain Philips NMS 8250) but I'm confused.

The test shows a time around:

real 0m0.180s
user 0m0.032s
sys 0m0.028s

But this time is much smaller than the time the program take to really open and close.
The time it takes from when icon appears on the dock to the time the program closes can be anywhere between 1s to 6s.
What is this discrepancy?
My impression is that the Mac Terminal is asking someone to open the emulator and reporting the job done without accounting the whole process.

Page 4/4
1 | 2 | 3 |