Good Window Apps - Help
-
I am looking for some guidelines on quality "Windows-Friendly" applications. I am trying to complete a project that has taken me some years to complete and running into some difficulty with windows. 1. I hate the memory management of Windows, it can't handle lots of calls to malloc() with small structures. I found by building large blocks of memory and obtaining nodes from it was better. Only, this adds additional code, and prohibits memory expansion. I think most applications use this same scheme, but looking for a better solution. 2. My program is a process, not an event-driven application. Therefore, a timer is required that calls the routine at a fixed interval so that the process can operate on the information. This appears to work, but not sure if Windows likes this. I like to set the timer between 50 and 200ms. Overall, the program functions, but Windows does not seem to like it. I don't have any problems with using Windows and other Win-based apps while my process is running, but when the process is complete and shutdown, Windows stays lethargic!? After awhile, Windows seems to wake up and operate more effectively. I would like some comments on what people do to overcome this. Is this a tuning issue, a memory problem (No Leaks!) or something else? Also, if one was ambitious, I could use some help. I am not a traditional Windows programmer, good C type though. Contact me at mfeldhake@ccoreinnovations.com if you are interested. I could offer some cash but would prefer some stock incentives (I’m incorporated). Person would need to be highly experienced in scientific applications. Thanks in Advance :-D Michael Feldhake www.ccoreinnovations.com
-
I am looking for some guidelines on quality "Windows-Friendly" applications. I am trying to complete a project that has taken me some years to complete and running into some difficulty with windows. 1. I hate the memory management of Windows, it can't handle lots of calls to malloc() with small structures. I found by building large blocks of memory and obtaining nodes from it was better. Only, this adds additional code, and prohibits memory expansion. I think most applications use this same scheme, but looking for a better solution. 2. My program is a process, not an event-driven application. Therefore, a timer is required that calls the routine at a fixed interval so that the process can operate on the information. This appears to work, but not sure if Windows likes this. I like to set the timer between 50 and 200ms. Overall, the program functions, but Windows does not seem to like it. I don't have any problems with using Windows and other Win-based apps while my process is running, but when the process is complete and shutdown, Windows stays lethargic!? After awhile, Windows seems to wake up and operate more effectively. I would like some comments on what people do to overcome this. Is this a tuning issue, a memory problem (No Leaks!) or something else? Also, if one was ambitious, I could use some help. I am not a traditional Windows programmer, good C type though. Contact me at mfeldhake@ccoreinnovations.com if you are interested. I could offer some cash but would prefer some stock incentives (I’m incorporated). Person would need to be highly experienced in scientific applications. Thanks in Advance :-D Michael Feldhake www.ccoreinnovations.com
iltallman wrote: 1. I hate the memory management of Windows, it can't handle lots of calls to malloc() with small structures. I found by building large blocks of memory and obtaining nodes from it was better. Only, this adds additional code, and prohibits memory expansion. I think most applications use this same scheme, but looking for a better solution. This is not a Windows restriction, this a restriction of your C/C++ Runtime Library. You need a better (for you) heap manager. Remember that a malloc call is not instantaneous. iltallman wrote: 2. My program is a process, not an event-driven application. Therefore, a timer is required that calls the routine at a fixed interval so that the process can operate on the information. This appears to work, but not sure if Windows likes this. I like to set the timer between 50 and 200ms. Huh? What are you trying to accomplish? Kant wrote: Actually she replied back to me "You shouldn't fix the bug. You should kill it"
-
I am looking for some guidelines on quality "Windows-Friendly" applications. I am trying to complete a project that has taken me some years to complete and running into some difficulty with windows. 1. I hate the memory management of Windows, it can't handle lots of calls to malloc() with small structures. I found by building large blocks of memory and obtaining nodes from it was better. Only, this adds additional code, and prohibits memory expansion. I think most applications use this same scheme, but looking for a better solution. 2. My program is a process, not an event-driven application. Therefore, a timer is required that calls the routine at a fixed interval so that the process can operate on the information. This appears to work, but not sure if Windows likes this. I like to set the timer between 50 and 200ms. Overall, the program functions, but Windows does not seem to like it. I don't have any problems with using Windows and other Win-based apps while my process is running, but when the process is complete and shutdown, Windows stays lethargic!? After awhile, Windows seems to wake up and operate more effectively. I would like some comments on what people do to overcome this. Is this a tuning issue, a memory problem (No Leaks!) or something else? Also, if one was ambitious, I could use some help. I am not a traditional Windows programmer, good C type though. Contact me at mfeldhake@ccoreinnovations.com if you are interested. I could offer some cash but would prefer some stock incentives (I’m incorporated). Person would need to be highly experienced in scientific applications. Thanks in Advance :-D Michael Feldhake www.ccoreinnovations.com
- Look at: "Fast memory allocation library for multithreaded applications " http://www.garret.ru/~knizhnik/sal.html[^] 2) I've seen this sort of behaviour on W9x I think where your app has allocated a large chunk of memory and when it shuts down it takes Windows a while to discard it from VM or something like that. You don't see this on NT based versions of Windows. If you are running NT/W2K/WXP and this is happening having a look in Task Manager Performance may shed some light on things. Neville Franks, Author of ED for Windows. Free Trial at www.getsoft.com