[asterisk-users] Dahdi for meetme on AMD64 arch?

[Tony Mountifield]

In article <4F168FCC.9070300 at jttech.se>, Johan Wilfer <lists at jttech.se> wrote:
> I'm in the process of replacing an old server with a new one and are
> making som changes in the infrastructure, the biggest change in my eyes
> is moving from i386 to AMD64 arch. Yesterday I began migrating some
> users from the old to the new server.
> 
> [...]
> 
> The old server (i386 Debian 5: Linux 2.6.26-2-openvz-686) can have 320
> calls in conferences without this problem.
> The new server (amd64 Debian 6: Linux 2.6.32-5-openvz-amd64) show these
> problems after 50 calls..
> 
> Old server:
> Hp dl360g5, 4 cpu Xeon E5420, 2.50GHz
> run i386 with PAE and OpenVZ, Debian Lenny
> uses the broadcom nic's on the motherboard
> asterisk 1.4.42 in openvz container (uses /dev/dahdi for timing)
> cacti shows cpu in kernel mode 80% with 320 active calls in conferences
> 
> New server:
> Hp dl360g7, 4 cpu Xeon E5520, 2.27GHz
> run amd63 with OpenVZ, Debian Squeeze
> uses Intel nic's 82571EB for offloading the processor + nic bonding in
> the kernel for failover.
> asterisk 1.4.42 in openvz container (uses /dev/dahdi for timing)
> cacti show cpu in kernel mod 100% with 57 active calls in conferences
> 
> This is a puzzle to me..
>  - Does anyone have experience with amd64 arch and dahdi for timing?
>  - Can Dahdi om amd64 be responsible for the high cpu in kernel mode?

It may be a stupid question just displaying ignorance on my part, but
why are you using *AMD*64 architecture on an *Intel* processor?
Surely for 64-bit, you should be using x86_64 architecture instead?

Cheers
Tony
-- 
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org