Pogledajte određenu poruku
Staro 27. 09. 2007.   #45
teknoledge
Milos Matovic
Qualified
 
Avatar teknoledge
 
Datum učlanjenja: 29.05.2007
Lokacija: Belgrader
Poruke: 157
Hvala: 15
11 "Hvala" u 6 poruka
teknoledge is on a distinguished road
Default

Citat:
Originalno napisao Misha Pogledajte poruku
:-) srchanim? Pre bi bilo da se cepanim od smeha samo ne vidis :-))) Pogledacu case studdy, samo zaboravio si da das link?!?! Ja sam od onih sto vole da se prica argumentima ... sorry :-)

Stvarno ne znam sta si nacuo i zasto si u zabludi da ima "drasticno" losije performanse od drugih CMS-a/Frameworka ... ili da su performanse al ikakav problem ...

Vec sam ti objasnio da postoje caching i throttle, vidim ne zanimaju te detalji oko toga nego aj jos jednom da ponovis tvrdjnu ... jel mislis da ce postati istina ako vise puta ponovis sta li :-)

Rails ima zaista uocljivo losije performanse od konkurencije al to ne sprecava ljude da ga koriste posto je al toliko bolji u mnogo cemu drugom, jer kada dodjes do toga da imas 100000 poseta dnevno imaces para za jos jedan server ... i za programera koji zna kako da podesi caching, throttle, opcode cache ... i tako ... kakve crne performanse ...

Ok, ovaj thread postaje dosadan polako
Cepanis, srchanis, sta god... Vidim da si od onih geek-ova koji "brane" odredjene applikacije po svaku cenu ko da su im deca...

Case study: http://drupal.org/node/116578
Web site: http://teamsugar.com/
Quote:

Citat:
1) Drupal has a hard time scaling with the number of modules and a lot of modules that a social network would want, e.g., the og module, are really bad performers. We get a lot of hits on the "my unread" page and it's absolutely brutal. Views also generate atrocious SQL which will pound your database into oblivion if you don't actively monitor the situation. We do not, for example, have a view for each block on the team homepage — the SQL is hand-written.

When you're creating web applications you're typically going for one of three things: speed/scalability, flexibility, or maintainability. Drupal is high on flexibility, average on maintainability, and poor on speed, in my opinion. If your priority is maintainability then I'd go for one of the RAD environments like Rails or CakePHP. If speed is your priority then I'd write your own lightweight framework, or whatever, and do it yourself.
Sad ces verovatno da kazes kako nisu optimizovali query-je, lose su napisali custom module, spori su im serveri, itd...

Ovo stvarno postaje dosadan thread jer si ga ti smorio....
teknoledge je offline   Odgovorite uz citat