Resource View Pregeneration

The assumptions I have are

  • Views have a definition that has its last modified date. For example, a Script that generates a JSON representation of a resource when the latter is modified by a Script.
  • Permanent resource storage has no storage restrictions

Now the situation is that I have resources for which their representations can be either pre-generated or generated on the fly; where the pre-generated one refers to text / html or application / atom + xml generated when the resource is changed (it can be executed asynchronously) and generated on the fly refers to, for example, the JSP / PHP Script view upon request.

What confuses me is how much pre-generation performance increase will be generated on the fly + caching ? What is your experience / opinion?

+3
source share
2

, , , , - .

- . - . , , , "", - .

, , ( ). :

  • ,

- , .

, :

  • , CPU,
  • , ,
  • , X (, ) 1000 (, X). , , .
+1

, ; , ( ), - .

, , , - , , .

0

Source: https://habr.com/ru/post/1763712/


All Articles