Re:Trojan found in Filezilla downloaded from SourceForge
by pmilot on Thursday December 03, 2015 @11:40AM
(#10670543)
The language used for a server backend is far from a guarantee of efficiency and performance. It's very easy to write a D or Rust backend that doesn't optimize queries and handles caching badly; you'll get just as terrible response times from those as you would on the "typical" slow websites that you refer to.
Re:Trojan found in Filezilla downloaded from SourceForge
by vortico on Thursday December 03, 2015 @09:45AM
(#10669782)
I don't know what you mean by fast, but https://www.ruby-forum.com/ seems to load pages faster than most websites, and as fast as D's forums.
Re:Trojan found in Filezilla downloaded from SourceForge
by shanemhansen on Thursday December 03, 2015 @12:12PM
(#10670781)
According to a quick check the forum.dlang.org initial page view takes 200ms. ruby-forum takes 738ms. If you want to talk RUM/page load metrics forum.dlang.org takes 800ms for the load event to fire, the ruby forum takes 1.6s.
Re:Trojan found in Filezilla downloaded from SourceForge
by osxrand on Thursday December 03, 2015 @02:04PM
(#10671762)
The individual posts load really quickly, but the main page doesn't (well not as fast as the other one mentioned). Either way, both are fast and I wish more websites were like this, not just forums!
Re:Trojan found in Filezilla downloaded from SourceForge
by GrinningFool on Thursday December 03, 2015 @11:29AM
(#10670472)
> Instead, it's all either slow, slow backend frameworks like Ruby, or even
Usually this is a matter of bad coding or overprovisioning of whatever is being used to host the site and the DB. Most maintained languages running on modern hardware can sustain reasonable loads without any significant performance issues. While client-side bad-performing frameworks abound, the last I looked into it, Ruby+Rails isn't that much worse or better than any other.
Re:Trojan found in Filezilla downloaded from SourceForge
by merb on Thursday December 03, 2015 @02:09PM
(#10671788)
It depends heavily on what you are doing.
Most CPU intensive Tasks are fast on everything. However on Memory intensive Applications Ruby and Python are really really aweful slow.
Re:Trojan found in Filezilla downloaded from SourceForge
by 83457 on Thursday December 03, 2015 @11:11AM
(#10670342)
most slowness you are talking about is usually database and/or caching related
Re:Trojan found in Filezilla downloaded from SourceForge
by 83457 on Thursday December 03, 2015 @01:04PM
(#10671282)
with that said, that forum is certainly blazing fast for page views
Re:Trojan found in Filezilla downloaded from SourceForge
by z3t4 on Thursday December 03, 2015 @04:48PM
(#10672917)
To be fair, the content of that forum could probably fit inside the RAM. And it's not doing anything fancy like sorting, etc.
[dead]
Instead, it's all either slow, slow backend frameworks like Ruby, or even worse, these SPA applications that require extensive client-side JS processing before they show you the goods.
Node is a step in the right direction for both problems: for the first, Node-based backend applications are faster than Ruby and Python, and for the client-side rendering problem, because Node can pre-render these SPA apps (which everyone should do for a serious production app that uses a framework/library like AngularJS or React for major client-side rendering).
But a server application based on D or Rust, or even Go, is an even better solution to the slow backend framework issue. Unfortunately, no one has yet created a full-service framework like Rails or Django for any of those languages.