Brian Wipf <[EMAIL PROTECTED]> writes:
> Nearly 100% of the CPU is going into pmap_remove_range. The stack
> trace for pmap_remove_range, viewable within Shark, is:
> -> pmap_remove_range
> --> pmap_remove
> ---> vm_map_simplify
> > vm_map_remove
> -> task_terminate_internal
> --> exi
On 3-Dec-07, at 3:51 PM, A.M. wrote:
On Dec 3, 2007, at 4:16 PM, Brian Wipf wrote:
We have a dual 3.0 GHz Intel Dual-core Xserve, running Mac OS X
10.5.1 Leopard Server and PostgreSQL 8.2.5. When we disconnect
several clients at a time (30+) in production, the CPU goes through
the roof and
On Dec 3, 2007, at 4:16 PM, Brian Wipf wrote:
We have a dual 3.0 GHz Intel Dual-core Xserve, running Mac OS X
10.5.1 Leopard Server and PostgreSQL 8.2.5. When we disconnect
several clients at a time (30+) in production, the CPU goes through
the roof and the server will hang for many second
We have a dual 3.0 GHz Intel Dual-core Xserve, running Mac OS X 10.5.1
Leopard Server and PostgreSQL 8.2.5. When we disconnect several
clients at a time (30+) in production, the CPU goes through the roof
and the server will hang for many seconds where it is completely non-
responsive. It see
