Forum OpenACS Development: Re: OpenACS performance issues

Collapse
Posted by Matthew Coupe on
The CPU is barely getting above 5-20% use.

It's almost as if when one person makes a request everyone else has to wait for their request before anything else happens.

From Postgresql conf
max_connections = 100
#---------------------------------------------------------------------------
# RESOURCE USAGE (except WAL)
#---------------------------------------------------------------------------

# - Memory -

shared_buffers = 32MB # min 128kB or max_connections*16kB
# (change requires restart)
#temp_buffers = 8MB # min 800kB
#max_prepared_transactions = 5 # can be 0 or more
# (change requires restart)
# Note: increasing max_prepared_transactions costs ~600 bytes of shared memory
# per transaction slot, plus lock space (see max_locks_per_transaction).
#work_mem = 1MB # min 64kB
#maintenance_work_mem = 16MB # min 1MB
#max_stack_depth = 2MB # min 100kB

# - Free Space Map -

max_fsm_pages = 204800 # min max_fsm_relations*16, 6 bytes each
# (change requires restart)
#max_fsm_relations = 1000 # min 100, ~70 bytes each
# (change requires restart)
.
.
.

These seem to take an age considering the CPU is so idle?

[05/Mar/2008:16:22:27][24412.2803030960][-conn:service0::15] Notice: --i ::3551196 DONE, ::3551196 -> (4774ms, 38
5ms)
[05/Mar/2008:16:22:36][24412.2806188976][-conn:service0::12] Notice: --starting... /campus/myprogramme/ , ::35512
22 -> (2806ms)
[05/Mar/2008:16:22:36][24412.2806188976][-conn:service0::12] Notice: --try index -> 0, ::3551222 ::xowiki::Packag
e->resolve_request (2809ms, 2ms)
[05/Mar/2008:16:22:36][24412.2806188976][-conn:service0::12] Notice: --after options, ::3551914 ::xowiki::Page->v
iew (3022ms, 213ms)