Hi,
> This machine is an old-school dual-Opteron 252 system and doesn't have > any hyperthreading support at all. > > Its exact configuration is > - 2 sockets > - 1 core per socket (2.6 GHz, 1MB cache) > - 2GB of RAM per socket > - 1 thread per core > > Having an hyperthreading-aware scheduler shouldn't make any difference; > what could explain the above performance differences ? > The heuristics I tested are about SMT (cache hotness heuristic - always tries to schedule on the last CPU that had run on. If we can't schedule on it and we are an cpu-bound process, we can wait for a tick to be ellected by our home CPU. If we aren't pulled after that, we are eligible and ready to be pulled on no matter what cpu). So, this heuristic doesn't have anything to do with HT (hyper threading). Mihai
