Logi WEBricka, mam ich dość!

Potrzebna pomoc
1

Cześć. Mam do Was pytanie odnośnie (za przeproszeniem) wkurwiających mnie logów z WEBrick’a (co prawda używam passengera - ale tam też są widoczne);

[code]Started GET “/assets/jquery.effects.highlight.js?body=1” for 127.0.0.1 at 2012-11-18 22:03:42 +0100
Served asset /jquery.effects.highlight.js - 304 Not Modified (5ms)
Served asset /application.css - 304 Not Modified (53ms)

Started GET “/assets/widgets.js?body=1” for 127.0.0.1 at 2012-11-18 22:03:42 +0100
Served asset /widgets.js - 304 Not Modified (2ms)[/code]
Jak się ich pozbyć?

2

https://github.com/evrone/quiet_assets

3

Albo prekompiluj assety, przy okazji będzie szybciej

4

Dzięki, działa. Teraz tylko jedno pytanie;

[code]➜ blog git:(master) ✗ passenger start
=============== Phusion Passenger Standalone web server started ===============
PID file: /home/bangeusz/Dokumenty/blog/tmp/pids/passenger.3000.pid
Log file: /home/bangeusz/Dokumenty/blog/log/passenger.3000.log
Environment: development
Accessible via: http://0.0.0.0:3000/

You can stop Phusion Passenger Standalone by pressing Ctrl-C.

Connecting to database specified by database.yml
Connecting to database specified by database.yml

Started HEAD “/” for 127.0.0.1 at 2012-11-19 16:07:59 +0100
Processing by NewsController#index as HTML
News Load (0.1ms) SELECT “news”.* FROM “news”
(0.1ms) SELECT COUNT() FROM “comments” WHERE “comments”.“news_id” = 1
Comment Load (0.1ms) SELECT “comments”. FROM “comments” WHERE “comments”.“news_id” = 1
User Load (0.1ms) SELECT “users”.* FROM “users” WHERE “users”.“id” = 1 LIMIT 1
CACHE (0.0ms) SELECT “users”.* FROM “users” WHERE “users”.“id” = 1 LIMIT 1
Rendered comments/_comment.html.haml (84.3ms)
Rendered news/index.html.haml within layouts/application (270.5ms)

Started GET “/” for 127.0.0.1 at 2012-11-19 16:08:00 +0100
Processing by NewsController#index as HTML
Completed 200 OK in 647ms (Views: 533.3ms | ActiveRecord: 4.5ms)
News Load (0.1ms) SELECT “news”.* FROM “news”
(0.1ms) SELECT COUNT() FROM “comments” WHERE “comments”.“news_id” = 1
Comment Load (0.1ms) SELECT “comments”. FROM “comments” WHERE “comments”.“news_id” = 1
User Load (0.1ms) SELECT “users”.* FROM “users” WHERE “users”.“id” = 1 LIMIT 1
CACHE (0.0ms) SELECT “users”.* FROM “users” WHERE “users”.“id” = 1 LIMIT 1
Rendered comments/_comment.html.haml (79.0ms)
Rendered news/index.html.haml within layouts/application (254.1ms)
Completed 200 OK in 621ms (Views: 505.2ms | ActiveRecord: 4.2ms)
Connecting to database specified by database.yml
Connecting to database specified by database.yml
Connecting to database specified by database.yml
Connecting to database specified by database.yml[/code]
Jednak bardziej chodzi mi o

Connecting to database specified by database.yml

Od czego jest to zależne? Od ilości zapytań?

@edit: A, wybaczcie. To tylko przy pierwszym requeście, potem jest w porządku.

5

te wpisy to najprawdopodobniej efekt connection-pooling, stąd pojawiają się przy starcie serwera.