If a job needs to be done, let it off, if it causes a problem, then worry, unless you're already anticipating a lot of backlash from co-workers.
You could move to asp.NET, and recode everything in C-Sharp, and COBOL and Perl and Basic, and QuickBasic <-- that would be wasting time.
your computer (server or your local desktop?) has a job to do, let it run and see how it behaves.
Given the answers you've supplied, I'm thinking that you're running scenarios on pricing structures to get yield curves.
If this is the case, and it's just for you and no-one else, you shouldn't have a problem, get a budget for a new PC, or just go have coffee and a cigarette when you're running this.
On a production server, you'd be taking a brave bit of time on one user kicking this off, but for a number of users, you'd be doing the machine a kindness by pulling the plug. This would be a DOS dream.
Is there any possibility of setting up a matrix of values, (it could be calculated on a different machine), and switch in the new values when the population is completed, and leave the webserver (if it is one) to handle serving data and pages rather than data, pages and calcs
Just my €0.02
--Paul
It's important in life to always strike a happy medium, so if you see someone with a crystal ball, and a smile on their face ... smack the fecker