Open andreituicu opened 4 months ago
Another possible optimisation is: We are using quite big break points for the images, because that is what is needed on the cards from the homepage/sidebar. These could be however parametrised, so we can use smaller images on the blog list cards, thus freeing bandwith to load bigger chunks of JSON info from the the index.
Actually, thinking about it, changing the size of chunks may not bring any benefits and might be even more harmful, because we use the same chunk size for all lookups for blogs (blog list, cards homepage, cards sidebars), which means we are maximising the requests that are being cached in the CDN and local browser. using different chunk sizes, will result in 2 distinct requests that are not cached.
We received the following customer feedback
The problem is:
Possible solutions:
blogs
sheet per language (blogs-en-US
,blogs-en-UK
, etc.) to make the search space smaller, but requires a bigger some refactoring, as there are multiple blocks using that sheet. The search space will keep growing as the new blogs are being published, but at a slower rate.