Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
node system
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
3 Apr 2014 at 13:19 UTC
Updated:
29 Jul 2014 at 23:31 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
wim leersComment #2
wim leersComment #3
jibranAgreed so RTBC.
Comment #4
znerol commentedPerhaps this is a stupid question, but what is the performance benefit of caching this block? If I'm not mistaken this will generate an additional trip to the cache backend (which possibly might be the database), while rendering it is just a matter of feeding some static array into
drupal_render. Has the render API really become slower than the database? Do we have benchmarks for that?Comment #5
webchickGood question.
Comment #6
wim leersI was in a "convert all the blocks" frenzy, but I agree. In fact, we should do precisely the opposite: prevent caching, because it's so ridiculously cheap to render. A cache get implies I/O, and I/O is always going to be more expensive than a very limited number of CPU cycles. Therefore, avoid I/O altogether.
Comment #7
wim leersComment #8
dawehnerReally wise observation!
Comment #9
webchickCommitted and pushed to 8.x. Thanks!
Comment #11
wim leers