# hops, latency on those hops sometimes makes little difference. ICMP traffic is generally treated as a very low priority, the route to a particular interface may take a completely different route than the server destination due to the fact that the router interface's usually have a small /30 taken out of a larger block, and anything longer than a /24 is generally filtered in the wider internet. A traceroute from your location to the server may indicate possible problems, but, the return path from the server may not be asymmetric. Traces from the server to your location would give you some idea as to whether that is the case.
There are a lot of things that affect page speed. If you are using firefox, get an extension called Lori (life of request info). Lori will tell you the time to first byte, time to transfer the page and the size of the page. Are the pages compressed, are the pages constructed well, is Pylons involved in serving static content rather than the webserver, are you running Apache/mod_wsgi, nginx, or paster? A page can serve quickly, but render very slowly due to javascript dependencies that haven't loaded. First thing is to figure out if it is a network issue, an application issue or a rendering issue. Do static pages/assets load quickly? Does the application do a lot of backend database work? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
