Difference between warmer and boost

Which "warmer" Module do you mean?

If I need to guess I think you are talking abound some kind of cache warmer module which provide no caching technology by itself. The Boost module itself is a caching module which brings additionally some cache warming functionality.

Are we talking about this warmer → module! This module is new to me. I will take a look. Maybe it's helpful to work on integration or reuse code.

Yes, you are right.

Thank you in advance.

@kazah I think your question is answered about the main difference boost is a cache module (with some warming functionality) and the warmer module seems to just provide warming functionality for different kind of cache situations..

Will boost provide better perfomance than warmer module?

Because Boost is only a page cache module we provide only warming on this caches which is provided by the CDN plugins of the warmer module. And this consumes lot's of resources. After a first look I cannot say if the warmer module or the boost module will do this more efficient because we need to trigger the webserver to serve all HTML pages we want.

I'm happy that also the warmer coder believe that sitemaps are a good page cache warming strategy. After a first test I currently miss basic authentication there for test servers. Maybe I will help the warmer module improve on this because they are using queues. And queues are a better strategy for very large content lists as the batch like we use for warming on boost. So especially because of modules like warmer I currently don't plan to extend boost on this feature and I will point on the warmer module for advanced features of warming. When the warmer module will fit all the things I believe the boost module is needing I maybe remove the warming features again from boost.

Thank you!

I'm waiting for the release of the boost to compare.

Automatically closed - issue fixed for 2 weeks with no activity.