If doubling of the number of users, much more than doubles the time to service each- what could be the cause ?
I’m thinking number of Amgrs or “run web agents concurrently”
It’s a simple website, with a WQO-agent to set up navigation based on the actual documents in the tree (read only).
Subject: 2 users: 2 seconds, 10 users: 100 seconds
Tomas,
What about the number of documents? Are they doubling (ie: does each new user create documents). Is the WQO doing an any inefficient lookups?
Mike
Subject: 2 users: 2 seconds, 10 users: 100 seconds
Web agents are not run by agent managers, so this explanation is ruled out.
Run web agents concurrently absolutely must be enabled, if you make use of WQO agents like that. From you posting, I cannot tell if it is.
Also, having a look at your code might help. Even 2 seconds doesn’t sound exactly fast for me, for a server on the local network.
Subject: 2 users: 2 seconds, 10 users: 100 seconds. Solved
Sorry for “disappearing”- the problem was, that some OLD visitor-logging code had been reactivated.
It tried to update some counter-documents on each document-open.
Counter-documents with thousands of conflicts - horrible mess.
I stopped that, and the responsetime fell from 200 to 0.2 seconds !
200 seconds (!) because the site was mentioned in the news repeatedly this morning.
That’s right, put me under pressure and I’ll improve performance 1000 fold : )
Subject: RE: 2 users: 2 seconds, 10 users: 100 seconds. Solved
“put me under pressure and I’ll improve performance 1000 fold”
LOL, that should give you quite a reputation, if you don’t talk to much about the old logging code … 