Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. System Admin
  4. Application losing a CPU while running

Application losing a CPU while running

Scheduled Pinned Locked Moved System Admin
question
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    jphillips
    wrote on last edited by
    #1

    Hi, I'm having some problems. We have an application that we made and when it runs on a dual CPU machine, we lose one CPU after a while. After checking, we found out that the Process Affinity was changed. We can set it back using the task manager but only to lose it again later. In no way in our code do we set the process affinity. But it seems to happen only when the CPUs are running at 100%. Can Windows (this was on Windows 2000, Service pack 3) decide to change the CPU access to an application by itself? Thanks, Jason Phillips

    R 1 Reply Last reply
    0
    • J jphillips

      Hi, I'm having some problems. We have an application that we made and when it runs on a dual CPU machine, we lose one CPU after a while. After checking, we found out that the Process Affinity was changed. We can set it back using the task manager but only to lose it again later. In no way in our code do we set the process affinity. But it seems to happen only when the CPUs are running at 100%. Can Windows (this was on Windows 2000, Service pack 3) decide to change the CPU access to an application by itself? Thanks, Jason Phillips

      R Offline
      R Offline
      Ray Cassick
      wrote on last edited by
      #2

      I would worry if you have CPU @ 100% on a dual machine. I would not be surprised if the OS took over and changed the settings to make sure that you app did not kill the box. Is this Win2k server or Pro?


      Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall."
      George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things."


      J 1 Reply Last reply
      0
      • R Ray Cassick

        I would worry if you have CPU @ 100% on a dual machine. I would not be surprised if the OS took over and changed the settings to make sure that you app did not kill the box. Is this Win2k server or Pro?


        Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall."
        George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things."


        J Offline
        J Offline
        jphillips
        wrote on last edited by
        #3

        It runs correctly on Windows XP. The problem only seems to be located on Windows 2000 Server/Pro. But I'm starting to think the same as you, in that the OS decides that the application is taking to much processing power and removes a CPU from the app.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups