Growing average time starting from 1000ms? That's a lot :-) If i try
request one page without database queries (and debug = 0), on our dev
server (local network) the response time is about 400ms. Our live
server is located somewhere else in the country with load balancing
enabled and usually responds way faster.
So for starters i'd recommend do what Martin suggested...
On 23 okt, 10:37, Alexey Grunichev <[EMAIL PROTECTED]> wrote:
> Thank you for comments.
>
> I've tested it on 2 computers first is desktop.
>
> CPU: Intel Pentium 4 3Ghz x 2, 2M Cache
> RAM: 2Gb
> HDD: WDC WD1600AAJS, 3Gb/s, 8M Cache, 7200rpm
> LAN: RTL8111/8168B PCIE Gigabit Etehrnet
> CentOS release 5 (Final), kernel 2.6.18.el5-i686
>
> Second is server:
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Xeon(R) CPU 3060 @ 2.40GHz
> stepping : 6
> cpu MHz : 2400.152
> cache size : 4096 KB
>
> Mem: 2074716k total
>
> Linux version 2.6.9-55.0.6.ELsmp ([EMAIL PROTECTED]
> bc2-3.build.redhat.com) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-8))
> #1 SMP Thu Aug 23 11:11:20 EDT 2007
>
> Installed on servers:
>
> Apache
> httpd 2.2.8 compiled with: --enable-rewrite --with-pcre=/usr/local/
> pcre
> configured with: ServerLimit 512 MaxClients 512 MaxSpareServers 24
>
> Memcached 1.2.5
> configured with: -d -P /tmp/memcached.pid -m 128 -u nobody
>
> MySQL 5.1.25-rc compiled with: --prefix=/usr/local/mysql-5.1.25-rc --
> with-plugins=innobase
> configured with: group_concat_max_len = 65536 max_connections = 500
> innodb_data_home_dir = /usr/local/mysql/var/
> innodb_data_file_path = ibdata1:100M:autoextend
> innodb_buffer_pool_size = 348M innodb_log_buffer_size 8M
> innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50
>
> PHP 5.2.6
>
> So, I don't think it's 386 :) And both computers are not shared
> hosting - there is no more running programs except of mine.
>
> Second remark - about requestActions etc, I know it's very slow, but
> there is another issue - the same results I receive if I test empty
> framework (without my code) with one page (/pages/test with simple
> echo "test"; view)
>
> I undderstand that CPU load may know nothing in this context, but
> system load average: 14.04 (and bigger too), so I think it's related.
>
> And very important - it didn't repeat when I retried this test with
> native-php (without framework) code.
>
> CPU usage is not important for user, but growing average time 1000 ms
> to max. time 50000 ms. is important for him, page loaded very long
> time, and I suppose it's depend on system overload (I don't get this
> growing time, for instance, with 10 Threads for example, because
> system is loaded, but not overloaded)
>
> Another remark, may be is may fault in first message "HTTP response
> times" in Jmeter summary statistics doesn't mean time_connect as for
> example in
> curl -o /dev/null -s -w %{time_connect}:%{time_starttransfer}:%
> {time_total}http://url/
> It's time between sending request and getting response with full HTML,
> so it's early (may be equal) to {time_total}
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
