icelava.net

Can you create a console .exe .NET program and put in an infinite while loop and run the program.While the program is running,can you check how much CPU's resources was being used and get back to me?I have a console application that is supposed to run 24/7,but it's a resource hog.So i'm tryin to find ways to fix it.

I had previously been looking for ways to throttle and limit the CPU usage as well but have not found a good way. What you can do is to lower the priority of the running thread so it does not take precedence over more important processes and threads.

icelava wrote:

I had previously been looking for ways to throttle and limit the CPU usage as well but have not found a good way. What you can do is to lower the priority of the running thread so it does not take precedence over more important processes and threads.

Is there a way to set the priority programtically?I'm surprised that a .net console application that does nothing,but runs an infinite 'while' loop would take up 100% CPU resources,not a good thing,i should say.

Yes you can make use of the Thread.Priority property.

Yes an endless loop, even when empty, does make the CPU do work (deciding if the condition is true or not).

I find it weird that a simple test condition can occupy up to 100% of the CPU's resources.Btw,if the thread is running an infinite loop,will it run infinitely or stop at some point?My program which was supposed to run 24/7 gets stopped due to some unknown reason after about 1 day of running.Basically,the code in the infinite loop check a table for data every 5 minutes,if there is data.The program will do some processing and then clear the table.Then it checks the table again every 5 minutes.

Gibby wrote:

I find it weird that a simple test condition can occupy up to 100% of the CPU's resources.

As much as I don't like it, an infinite loop does tell the CPU to do some work.

Basically,the code in the infinite loop check a table for data every 5 minutes,if there is data.The program will do some processing and then clear the table.Then it checks the table again every 5 minutes.

You are better off developing a one-run sequence program that does this check and using Task Scheduler to launch it every 5 minutes.

icelava wrote:

You are better off developing a one-run sequence program that does this check and using Task Scheduler to launch it every 5 minutes.

The only problem with the one run sequence is that if the program takes longer than 5 minutes to execute it's stuff.Then after 5 minutes is up,the task scheduler will open up another instance of that program as the current one is still doing some processing.With 2 instances accessing the same database,data corruption could occur,plus the interval can't be staggered more than 5 minutes as it needs to check the database within small time period intervals,so 5 minutes is the max between each checking.

You can make the program a singleton, so only an instance may run at any point of time. I do not have the code handy now but you can check if another instance is already running, and exit if so.

icelava wrote:

You can make the program a singleton, so only an instance may run at any point of time. I do not have the code handy now but you can check if another instance is already running, and exit if so.

Never mind,i've handed that project to someone else,it's her problem now.