Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When moving my .Net Compact Framework application to the SD-card of a Windows CE device, the program executes slower then running it from the internal memory.
I thought, the start-up might be slower, but it is the whole program. There is no IO to the storage card.
Why is my application so slow and how does the compact framework handles and loads the assemblies?
It has to do with demand-paging. Your app cannot be run directly from the SD-card, as SD is not executable media so it has to be pulled into RAM to run. Windows CE doesn’t typically have a whole lot of RAM, so the loader doesn’t pull your entire application into RAM to run. Sure, your heaps and stacks will be in RAM, but the actual IL code in the assembly itself is paged in as needed. It’s also paged out when the system decides it no longer needs a specific page.
This paging can have an impact on performance, though I’m a bit surprised that it’s a large impact unless the app itself is really large (like if you have lots of embedded resources that it’s pulling out of the assembly).