Printable View
Thanks for that wonderful update.
My first tests have been OK but I notice that all java applications/applets generated by MMF use 100% of the CPU which may slowdown the apps but also drain the laptops autonomy.
Most applets I tried don't seem to use so much CPU. Is there some optimization planed or is it the way they are supposed to work for a while.
To get a good synchrosinsation, I need to make application sleep a little time. The rest is down to Java engine.
I am sure this 100% time is not REAL 100% time. So far when my test Java apps were running, I could use my machine OK. This is just a problem with Windows task manager.
True.
I never got any application to reach 100% CPU on my computer without setting its process priority higher, but yes, Java apps made by MMF2 takes 50% CPU.
No, that's an illusion created by having dual core processors, LIJI.
Yes it is not "real" 100% CPU usage or even moving the mouse pointer would be choppy. If I remember it is something about "idle" stuff, the way CPU is allocated to applications. MMF1.5 and older Macromedia Director versions acted the same showing a 100% CPU activity on the task manager, despite not using trully those 100%.
However MMF2 built apps -unlike MMF1.5's - show "normal" CPU usage so maybe there is a way to do the same with java exported applications ?
The problem here is with laptops energy management system that think the CPU is overheating and force unnecessarily the fans to turn permanently which is a little annoying (drains power and can be noisy).
I wonder if it is specific to Windows or if it behaves the same with linux or macs ?
If Task manager says 100% cpu, then the app is using 100% cpu, even if it's just spinning in a loop waiting for something else.
As the mouse is interrupt-driven, it tends not to get choppy unless an application is doing a lot of disk access (which stalls the cpu) or graphics (which can stall the drawing of the mouse).
EDIT: On Windows (i.e. not Java), you can have your program sit in a loop doing PeekMessage(), handling any messages that come along (eg mouse clicks) and then doing whatever it wants when there are no messages (idle-time processing). Once your app is done, it can either spin in a loop continuously peeking until it either decides to do more work or a message comes along (which results in 100% cpu, despite doing nothing), or it can use sleep(time) to actually do nothing more for a certain amount of time, or WaitMessage() to do nothing more until a new message arrives (which could be a timer, to give a similar effect to sleep). I presume MMF2 uses one of the later two, and MMF1.5 and before used the first.
Yes I agree, that means that the application uses all the CPU that Windows gives it. Hopefully it's possible to change it.Quote:
If Task manager says 100% cpu, then the app is using 100% cpu