Re: TTFB, Apache, Seaside Performance Problem

Mariano, no, there is no difference in the response time between localhost
and 127.0.0.1
I entered now the ip of the server there.

Don't you think that this should be written in the book?
http://book.seaside.st/book/advanced/deployment/deployment-apache/configure-apache



2017-01-05 12:58 GMT+01:00 Mariano Martinez Peck [via Smalltalk] <
[email protected]>:

> Wow, that's what I call to nail it! hahahaha.
>
> Norbert, do you have some explanation we could all learn from it? It's
> something concrete about Apache or is it something as general as resolving
> localhost could take longer than 127.0.0.1?
>
> Sabine, do you see a difference in the response time  when ping to
> localhost and 127.0.0.1 ?
>
> Thanks in advance,
>
> On Thu, Jan 5, 2017 at 8:47 AM, Sabine Manaa <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=4928845&i=0>> wrote:
>
>> The problem is solved: I had to replace localhost by 127.0.0.1
>> Thanks a lot Norbert Hartl for your advice!
>>
>> 2017-01-05 12:25 GMT+01:00 Sabine Manaa [via Smalltalk] <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=4928844&i=0>>:
>>
>>> Hi,
>>>
>>> I need the help of the community.
>>>
>>> I am not succeding in making our app faster.
>>> The problem is the Time to first Byte (TTFB). It is always more than one
>>> second which is much to much.
>>> We reduced the problem to a problem between apache and pharo/seaside.
>>>
>>> For this, I have a test application which only renders "hello World". So
>>> I am sure it is not my code, my database, my css, my js, my ssl.... :-)
>>>
>>> I optimized and learned a lot for my app, but it did not solve the TTFB
>>> problem, which costs 1 additional sec for each click of the user which is
>>> inaceptable.
>>>
>>> Please follow this tests to see the problem:
>>>
>>> ===>>> Test 1: test.html without Pharo/seaside
>>> https://tools.keycdn.com/performance?url=http://app.spesenfu
>>> chs.de/test.html
>>> TTFB in Frankfurt below 10 ms -> this proves that the server and
>>> configuration is fast.
>>>
>>> ===>>> Test 2: hello world, simple seaside page
>>> https://tools.keycdn.com/performance?url=app.spesenfuchs.de/hello
>>> TTFB in Frankfurt more than 1 second! -> this proves that it is not my
>>> application :-) it is only a hello world seaside page...
>>>
>>> ===>>> Test 3: my login page
>>> https://tools.keycdn.com/performance?url=app.spesenfuchs.de/rka
>>> TTFB in Frankfurt more than 1 second!
>>>
>>> (alternative: enter the urls into https://gtmetrix.com/)
>>>
>>> In Apache, we enabled tracing of the rewrite and this tells me (i
>>> assume), that apache makes the rewrite very fast, within the same
>>> millisecond :-)
>>> [Thu Jan 05 12:14:35.243400 2017] [rewrite:trace2] [pid 1288:tid 1692]
>>> mod_rewrite.c(477): [client 91.89.219.232:52272] 91.89.219.232 - - [
>>> app.spesenfuchs.de/sid#66c848][rid#20bc4c8/initial
>>> <http://app.spesenfuchs.de/sid#66c848][rid%2320bc4c8/initial>] init
>>> rewrite engine with requested uri /hello
>>> [Thu Jan 05 12:14:35.243400 2017] [rewrite:trace3] [pid 1288:tid 1692]
>>> mod_rewrite.c(477): [client 91.89.219.232:52272] 91.89.219.232 - - [
>>> app.spesenfuchs.de/sid#66c848][rid#20bc4c8/initial
>>> <http://app.spesenfuchs.de/sid#66c848][rid%2320bc4c8/initial>] applying
>>> pattern '^/rka(.*)$' to uri '/hello'
>>> [Thu Jan 05 12:14:35.243400 2017] [rewrite:trace3] [pid 1288:tid 1692]
>>> mod_rewrite.c(477): [client 91.89.219.232:52272] 91.89.219.232 - - [
>>> app.spesenfuchs.de/sid#66c848][rid#20bc4c8/initial
>>> <http://app.spesenfuchs.de/sid#66c848][rid%2320bc4c8/initial>] applying
>>> pattern '^/hello(.*)$' to uri '/hello'
>>> [Thu Jan 05 12:14:35.243400 2017] [rewrite:trace2] [pid 1288:tid 1692]
>>> mod_rewrite.c(477): [client 91.89.219.232:52272] 91.89.219.232 - - [
>>> app.spesenfuchs.de/sid#66c848][rid#20bc4c8/initial
>>> <http://app.spesenfuchs.de/sid#66c848][rid%2320bc4c8/initial>] rewrite
>>> '/hello' -> 'http://localhost:8085/HelloWorld/'
>>> [Thu Jan 05 12:14:35.243400 2017] [rewrite:trace2] [pid 1288:tid 1692]
>>> mod_rewrite.c(477): [client 91.89.219.232:52272] 91.89.219.232 - - [
>>> app.spesenfuchs.de/sid#66c848][rid#20bc4c8/initial
>>> <http://app.spesenfuchs.de/sid#66c848][rid%2320bc4c8/initial>] forcing
>>> proxy-throughput with http://localhost:8085/HelloWorld/
>>> [Thu Jan 05 12:14:35.243400 2017] [rewrite:trace1] [pid 1288:tid 1692]
>>> mod_rewrite.c(477): [client 91.89.219.232:52272] 91.89.219.232 - - [
>>> app.spesenfuchs.de/sid#66c848][rid#20bc4c8/initial
>>> <http://app.spesenfuchs.de/sid#66c848][rid%2320bc4c8/initial>] go-ahead
>>> with proxy request proxy:http://localhost:8085/HelloWorld/ [OK]
>>>
>>> So, I assume that there is problem between Apache and Seaside....
>>>
>>> My questiond are:
>>> what can I do to find the bottleneck?
>>> what is the reason that is so slow?
>>> your help is very appreciated because I have run out of ideas what it
>>> could be and I was investigating it several days now.
>>>
>>> Concerning the system:
>>> The server is at Amazon ec2 windows Server 2009 R2 SP1
>>> The Apache version is 2.4.23
>>> The configuration of the apache is like this (as described in the
>>> seaside book http://book.seaside.st/book/ad
>>> vanced/deployment/deployment-apache/configure-apache)
>>>
>>> <VirtualHost *:80>
>>>       ProxyPreserveHost On
>>>       ServerName app.spesenfuchs.de
>>>       RewriteEngine On
>>> <Directory "C:\xampp\htdocs">
>>>         Require all granted
>>> </Directory>
>>>      DocumentRoot "C:\xampp\htdocs"
>>>      RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
>>>
>>>     RewriteRule ^/rka(.*)$ http://localhost:8085/RKA/$1 [proxy,last]
>>>    RewriteRule ^/hello(.*)$ http://localhost:8085/HelloWorld/$1 [proxy,last]
>>>
>>> </VirtualHost>
>>>
>>> ------------------------------
>>> If you reply to this email, your message will be added to the discussion
>>> below:
>>> http://forum.world.st/TTFB-Apache-Seaside-Performance-Proble
>>> m-tp4928842.html
>>> To start a new topic under Seaside General, email [hidden email]
>>> <http:///user/SendEmail.jtp?type=node&node=4928844&i=1>
>>> To unsubscribe from Seaside, click here.
>>> NAML
>>> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>>
>>
>>
>> ------------------------------
>> View this message in context: Re: TTFB, Apache, Seaside Performance
>> Problem
>> <http://forum.world.st/TTFB-Apache-Seaside-Performance-Problem-tp4928842p4928844.html>
>> Sent from the Seaside General mailing list archive
>> <http://forum.world.st/Seaside-General-f86180.html> at Nabble.com.
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4928845&i=1>
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
> _______________________________________________
> seaside mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4928845&i=2>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://forum.world.st/TTFB-Apache-Seaside-Performance-
> Problem-tp4928842p4928845.html
> To start a new topic under Seaside General, email
> [email protected]
> To unsubscribe from TTFB, Apache, Seaside Performance Problem, click here
> <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4928842&code=bWFuYWEuc2FiaW5lQGdtYWlsLmNvbXw0OTI4ODQyfC0xOTE3OTcxOTg5>
> .
> NAML
> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://forum.world.st/TTFB-Apache-Seaside-Performance-Problem-tp4928842p4928846.html
Sent from the Seaside General mailing list archive at Nabble.com.

_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside