3 ms·
I was on a Rails project with some pages spending 200ms or more rendering views. To some extent that could have been got around by inlining partials or getting
by bluesnowmonkey 14y ago
I was on a Rails project with some pages spending 200ms or more rendering views. To some extent that could have been got around by inlining partials or getting very clever with cache invalidation, but it would have come at a high cost in terms of complexity. Maybe a C++ framework could hit the performance/complexity sweet spot better. Then again, the site's down, so maybe not.
- klickverbot 14y agoThe site is/was hosted on a Wordpress instance… ;)
- xiaoma 14y agoTo be fair, though the error I'm seeing blames the database (エラー: データベースに接続できません).
- carsongross 14y agoI agree that one area where rails could improve is in the string serialization/ERB component (e.g. includes shouldn't materialize a string then write, but should concat to the current output for example) but ruby strings are pretty damned fast in my experience. I believe that's an implementation detail that could be addressed without going to C++.