[rt-users] performance problem - RT3.0.3 on Postgresql 7.3.3 (solution)
Asif Iqbal
iqbala at qwestip.net
Tue Jul 1 01:25:25 EDT 2003
On Fri, 27 Jun 2003, Paul Wagland wrote:
> And more importantly :-) (Given that this is the request that people are
> saying is really slow)
>
> This is also from ab:
>
> old:
> ----
> Document Path: /rt3/Ticket/Update.html?Action=Respond&id=1003
> Document Length: 9261 bytes
>
> Concurrency Level: 1
> Time taken for tests: 214.115 seconds
> Complete requests: 20
>
> Percentage of the requests served within a certain time (ms)
> 50% 10529
> 66% 10687
> 75% 10822
> 80% 11066
> 90% 11943
>
I am just curious about how did you generate an output like that
>
> new:
> ----
> Document Path: /rt3/Ticket/Update.html?Action=Respond&id=1003
> Document Length: 9261 bytes
>
> Concurrency Level: 1
> Time taken for tests: 18.344 seconds
> Complete requests: 20
>
> Percentage of the requests served within a certain time (ms)
> 50% 796
> 66% 827
> 75% 848
> 80% 891
> 90% 1018
--
Asif Iqbal
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08
There's no place like 127.0.0.1
More information about the rt-users
mailing list