Changes between Initial Version and Version 1 of Ticket #7785, comment 34
- Timestamp:
- Jun 4, 2015, 10:28:39 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #7785, comment 34
initial v1 1 1 Nobody just payed attention in the client side? 2 Just try to load the page with "nc" (NetCat). 2 Just try to load the page with "nc" (netcat). 3 3 4 In my problem (I guess it is not the same as it bug but may be related in the client side) I noticed a very very slow page load in all pages of the trac 0.12b1 with all the rest (Python, SQLite, etc) updated. A very very slow page loading in all sections (no matters where). I just guessed it is a slowdown in trac. 5 4 6 I'm using trac.fcg in an apache web server with mod-fastcgi. It was working perfect in my old server (software, the hardware is new 4GB RAM dual channel and so). I just do an software upgrade (Installed Ubuntu 9.10 server) and reconfigured all the system to the new distro (I was using LFS an oldest one 5 years old). 7 5 8 I noticed that loading trac.fcg pages was very slow from my own computer! 9 6 10 I tried with top, gdb, and a lot of other workarounds to take account in what happening there. top just showed 0% cpu load most of the time. The global system load was near 0. So?? Where is the problem? The system have full power to server the request and? Maybe a network problem... I tested the communication with fastcgi spawned processes and all is ok/faster enought! Too fast for my like! 7 So I decided to load that page from NetCat: 11 12 So I decided to load that page from netcat: 13 {{{ 8 14 nc servidor 80 9 15 GET /page/trac.fcg/proyect 10 16 }}} 11 17 What I get is the page what I was espectind but very fast! 12 18 So the problem is my client navigator: Firefox. 13 19 I tested with Epiphany and yes, Epiphany loaded it very faster. 14 15 20 Continiung the tests I noticed a firefox halt in: 16 21 {{{#!xml 17 22 <script type="text/javascript">/*<![CDATA[*/ 18 23 jQuery(document).ready(function($) { … … 25 30 }); 26 31 /*]]>*/</script> 32 }}} 33 mmm, that maybe the problem. 27 34 28 mmm, that maybe the problem.29 35 I will try updating jquery so including an updated version in my own Trac system. 30 36 Why I'm writting this here? Because you need to pay attention too to the client side. Some slowdowns may be clientside scripts, so you must too correct that scripts for that. And why not rewrite some portions to be more webbrowser friendly. 31