SMP

SMP

Post by abzces » Mon, 06 Jan 2003 19:14:38



I have been running FreeBSD for a couple years now, but have not had any
experience with multiple processors.  I will soon be setting up some *
servers on a box with 4 processors, and would like to "assign" each of the 3
servers a specific processor, while leaving the fourth entirely to system
processes and the like.
Can someone please refer me to some documentation that can help me to
achieve this goal?

--Abzcess

 
 
 

SMP

Post by Anne On Imu » Mon, 06 Jan 2003 19:28:42



> I have been running FreeBSD for a couple years now, but have not had
> any experience with multiple processors.  I will soon be setting up
> some * servers on a box with 4 processors, and would like to
> "assign" each of the 3 servers a specific processor, while leaving the
> fourth entirely to system processes and the like. Can someone please
> refer me to some documentation that can help me to achieve this goal?

> --Abzcess

The idea here is to try to use threaded server processes, and trust (and
tune) the OS to keep the processors busy with them.  This may involve
you just sitting there watching it, and renicing the game server process(
es), to changing up and pruning your set of daemons etc.

 
 
 

SMP

Post by those who know me have no need of my nam » Tue, 07 Jan 2003 05:51:09


in comp.unix.admin i read:

Quote:>I will soon be setting up some * servers on a box with 4 processors,
>and would like to "assign" each of the 3 servers a specific processor,
>while leaving the fourth entirely to system processes and the like.  Can
>someone please refer me to some documentation that can help me to achieve
>this goal?

the word you are looking for is `affinity'.  you can fixate a process onto
a single processor by setting the affinity.  sometimes that makes sense,
sometimes it doesn't.

--
bringing you boring signatures for 17 years

 
 
 

SMP

Post by Daxber » Wed, 08 Jan 2003 16:38:49


FYI-

CPU affinity makes a lot of sense when you take into account CPU cache.
Since each CPU has it's own internal cache, it's better to have CPU
intensive processes "stick" to one CPU.

Let's take setiathome for example... If I had 4 processors, I'd run 4
instances of seti and bind each game to a specific CPU.  This will permit
each CPU's cache to be the most effective.  You can't do much about the
other OS process requirements, just let the OS decide which process to
context switch.  I feel it would be a waste of the 4th CPU to not have it
also run seti.

Also... How would you set affinity with FreeBSD?  With Solaris it's pbind...
no clue about BSD.

Anyone?



Quote:> in comp.unix.admin i read:

> >I will soon be setting up some * servers on a box with 4 processors,
> >and would like to "assign" each of the 3 servers a specific processor,
> >while leaving the fourth entirely to system processes and the like.  Can
> >someone please refer me to some documentation that can help me to achieve
> >this goal?

> the word you are looking for is `affinity'.  you can fixate a process onto
> a single processor by setting the affinity.  sometimes that makes sense,
> sometimes it doesn't.

> --
> bringing you boring signatures for 17 years

 
 
 

SMP

Post by those who know me have no need of my nam » Tue, 14 Jan 2003 19:31:26


in comp.unix.admin i read:

Quote:>CPU affinity makes a lot of sense when you take into account CPU cache.
>Since each CPU has it's own internal cache, it's better to have CPU
>intensive processes "stick" to one CPU.

can be.  but as always `it depends'.  the op wants to run game servers,
each to a cpu.  okay that sounds fine, but what if a cpu dies, should the
associated game die too?  if it's been bound to a single cpu that's what
will happen.  most likely a quad cpu system running four game servers will
likely have one server per processor purely due to the normal scheduling.
(if the hardware is *then the whole system will probably die anyway so
perhaps it's not a bad thing to force the affinities.)

Quote:>Also... How would you set affinity with FreeBSD?  With Solaris it's pbind...
>no clue about BSD.

nothing yet.

--
bringing you boring signatures for 17 years

 
 
 

1. SMP - zombie processes with SMP enabled ...

My Linux 2.0.20 with SMP = 1 uncommented generates more and more zombie
processes. This happens if I start programs from different virtual console
sessions. My equippment is a ASUS P/E-P55T2P4D with  a pair of  Intel
120MHz Pentiums and 64 Megs of main memory.

Has anyone an idea whats going wrong here?

Your suggestions would be appreciated ...

Martin

2. Computing VM Usage?

3. SMP motherboards (760 MPX chipset) and SMP howto

4. bootpd[115821]: error

5. Booting SMP kernel on non-SMP machines?

6. Sportster Flash: what is it?

7. Best NIC card -- LInux 2.4 SMP -> LInux 2.4 SMP

8. Viewing Quicktime on Linux

9. assertion failure : ext3 & lvm , 2.4.17 smp & 2.4.18-ac1 smp

10. FreeBSD 3.1 SMP outperforms SuSE Linux 6.0 SMP by 230 percent

11. SMP: Tyan Tomcat III dual, only one CPU active in /proc/smp

12. Pentium Pro SMP - scsi disks timing out at boot, only with SMP

13. List of SMP Boards that are known to Work with SMP LINUX.