Strange Behavior on Gulp Remember

[ahaurw01]

Strange Behavior on Gulp Remember

[ahaurw01]

I haven't fully grokked what you're doing here, but it looks like the problem might be due to using only a single named remember cache (remember('imageResize')) when you might be dealing with multiple sets of files that need to be remembered in their own separated spaces. Could it be that you need a differently named remember cache for each queue you're filling up?

[rizalp]

What I would like to do, is caching the image read into memory. Since the Image is quite large (> 10MB), I think it would be faster and lighter on memory if we only read the Image once, and then down the pipeline operate on that set of cache...

Using different cache name for different presets (like remember('imageResizeHD720')) would defeat that purpose. Or, am I doing something wrong here?

[ahaurw01]

@rizalp Apologies for the delay in getting back to you. Were you able to find the approach you needed? If you think you came across a weakness of this plugin, I'd be quite grateful for a failing test case.

[rizalp]

Hi there. I realized that the things that I want to do is actually not the way it is supposed to be. I'd like to cache all image file into memory, and output it into several resolution presets with different pipeline. At first I tought that gulp-cached and gulp-remember fit my needs, but actually it is not.

And so, I didn't use it in this task. Besides, OS already do some caching with the read in the buffer. So all is good enough for me